Re: Can you tell me function name that means 'Entry Point: 0x11000000' ?
Ahmed Ammar <[email protected]>
| Newsgroups | gmane.comp.micro-kernel.l4.devel |
|---|---|
| Message-ID | <[email protected]> |
Attached is the patch we use for the saber_sd’s uart1: On Mar 21, 2014, at 5:02 PM, Matthias Lange <[email protected]> wrote: > Hi, > >> On 21 Mar 2014, at 11:33, Taeung <[email protected]> wrote: >> >> Hello, l4 hacker. >> >> >> I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE SD board(Cortex-A9, ARMv7). >> >> I'm using 'u-boot' and 'uImage'. >> So, i build uimage by "make uimage E=hello ~...". >> And i've try to booting it on Freescale i.MX6q_sabre_sd board. >> But i did not it because stoped at "Starting kernel ..." !! > > Probably you selected the wrong UART, so the system is not printing something on the serial line. Make sure you have the right UART driver for your platform and make sure you have selected the right one. Usually there are more than one UARTs and only one is connected to you serial line. You can also check Linux to see which UART it uses. > >> MMC read: dev # 2, block # 2048, count 8192 ... 8192 blocks read: OK >> ## Booting kernel from Legacy Image at 10800000 ... >> Image Name: L4 Image #2 >> Image Type: ARM Linux Kernel Image (uncompressed) >> Data Size: 868352 Bytes = 848 kB >> Load Address: 11000000 >> Entry Point: 11000000 >> Loading Kernel Image ... OK >> OK >> >> Starting kernel ... >> >> >> uimage's file name is "bootstrap_hello.uimage". >> "bootstrap_hello.uimage" has information such as >> "bootstrap_hello.uimage: u-boot legacy uImage, L4 Image #2, Linux/ARM, OS Kernel Image (Not compressed), 868352 bytes, >> Thu Mar 20 13:14:42 2014, Load Address: 0x11000000, Entry Point: 0x11000000, Header CRC: 0xBEA251F3, Data CRC: 0xA0217B7D" >> >> I have a question. >> >> Can you tell me function name that means 'Entry Point: 0x11000000' ? > > In the uimage format the entry point is defined as the address where uboot should start, as the name implies, the execution of the image. > > > Matthias. > _______________________________________________ > l4-hackers mailing list > [email protected] > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers _______________________________________________ l4-hackers mailing list [email protected] http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
sabre_sd_uart.patch
(application/octet-stream, 1.9 KB)
commit 093100350bbff65b08ad6255e4f2c827d3cf54d3 Author: Ahmed Ammar <[email protected]> Date: Tue Sep 17 17:20:18 2013 +0200 sabresd: change to uart1 diff --git a/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp b/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp index 1b849b7..df03cfc 100644 --- a/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp +++ b/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp @@ -109,7 +109,7 @@ public: Watchdog_map_base = Devices2_map_base + 0xbc000, // wdog1 Gpt_map_base = Devices2_map_base + 0x98000, Src_map_base = Devices2_map_base + 0xd8000, - Uart_base = Uart2_map_base, + Uart_base = Uart1_map_base, }; enum Phys_layout_imx6 : Address { diff --git a/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp b/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp index 7f6e572..a704645 100644 --- a/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp +++ b/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp @@ -41,7 +41,9 @@ IMPLEMENTATION [imx6]: #include "uart_imx.h" -IMPLEMENT int Uart::irq() const { return 59; } +// uart-1: 58 +// uart-2: 59 +IMPLEMENT int Uart::irq() const { return 58; } IMPLEMENT L4::Uart *Uart::uart() { diff --git a/l4/pkg/bootstrap/server/src/platform/imx.cc b/l4/pkg/bootstrap/server/src/platform/imx.cc index e328deb..82ba849 100644 --- a/l4/pkg/bootstrap/server/src/platform/imx.cc +++ b/l4/pkg/bootstrap/server/src/platform/imx.cc @@ -124,8 +124,8 @@ class Platform_arm_imx : public Platform_single_region_ram /* End Neon Setup */ - //static L4::Io_register_block_mmio r(0x02020000); // UART1 - static L4::Io_register_block_mmio r(0x021e8000); // UART2 + static L4::Io_register_block_mmio r(0x02020000); // UART1 + //static L4::Io_register_block_mmio r(0x021e8000); // UART2 static L4::Uart_imx6 _uart; #else #error Which platform type?