[U-Boot-Users] Preliminary patch for Cogent CBS336 (MC9328MXL-based)
Starting from Bryan Larsen's patch for U-Boot 0.4.0, I started porting U-Boot 1.1.2 on Cogent CSB336. The patch against current CVS is available for download here http://www.dave-tech.it/download/misc/up-csb336-1 (I could not attach because the size limit). Some clean ups are needed here and there. I had to change the routine reset_timer_masked in cpu/mc9328/interrupts.c (bug?). To initialize clocks and SDRAM controller I used the same values used by the Micromonitor bootloader the board comes with. I also had to avoid invoking funtion SetAsynchMode() otherwise the processor hangs.
U-Boot seems to be stable but I could not load Linux kernel so far. I'm trying to start a modified version of the kernel 0.3.8 delivered by Motorola for the M9328MXL ADS. It seems the kernel does not like the parameters passed by U-Boot. Still working on it. Any advice or suggestion is appreciated.
Regards,
llandre
DAVE Electronics System House - R&D Department www.dave-tech.it
U-Boot seems to be stable but I could not load Linux kernel so far. I'm trying to start a modified version of the kernel 0.3.8 delivered by Motorola for the M9328MXL ADS. It seems the kernel does not like the parameters passed by U-Boot. Still working on it. Any advice or suggestion is appreciated.
Use linux 2.6.7 with the i.MX patch from pengutronix. This works fine.
http://www.pengutronix.de/software/linux-i.MX/v2.6/
BTW: Sascha Hauer already posted a patch for the i.MX! It's still in Wolfgang's queue. Have a look at
http://www.pengutronix.de/software/u-boot/u-boot-imx1-20040628-1.diff
Steven
Hi Steven,
thanks a lot for your support. I tried to run the patched 2.6.7 kernel but it seems it hangs after decompression (don't see further messages):
Bytes transferred = 753884 (b80dc hex) ## Booting image at 08800000 ... Image Name: Linux-2.6.7-imx3 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 753820 Bytes = 736.2 kB Load Address: 08008000 Entry Point: 08008000 Verifying Checksum ... OK OK ## Loading Ramdisk Image at 10240000 ... Image Name: B2EVB romfs Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 442554 Bytes = 432.2 kB Load Address: 0c400000 Entry Point: 0c400000 Verifying Checksum ... OK ## Transferring control to Linux (at address 08008000) ...
Starting kernel ...
Uncompressing Linux..................................................... done, booting the kernel.
I'll perform further investigations. In case it actually won't work, I'll patch U-Boot with Sascha's latest patch and I'll try again.
Regards, llandre
DAVE Electronics System House - R&D Department www.dave-tech.it
U-Boot seems to be stable but I could not load Linux kernel so far. I'm trying to start a modified version of the kernel 0.3.8 delivered by Motorola for the M9328MXL ADS. It seems the kernel does not like the parameters passed by U-Boot. Still working on it. Any advice or suggestion is appreciated.
Use linux 2.6.7 with the i.MX patch from pengutronix. This works fine.
http://www.pengutronix.de/software/linux-i.MX/v2.6/
BTW: Sascha Hauer already posted a patch for the i.MX! It's still in Wolfgang's queue. Have a look at
http://www.pengutronix.de/software/u-boot/u-boot-imx1-20040628-1.diff
Steven
Hi llandre,
thanks a lot for your support. I tried to run the patched 2.6.7 kernel but it seems it hangs after decompression (don't see further messages): ... ## Transferring control to Linux (at address 08008000) ...
Starting kernel ...
Uncompressing Linux..................................................... done, booting the kernel.
I bet it does not hang. It's probably just the wrong settings for serial console!
Steven
thanks a lot for your support. I tried to run the patched 2.6.7 kernel but it seems it hangs after decompression (don't see further messages): ... ## Transferring control to Linux (at address 08008000) ... Starting kernel ... Uncompressing Linux..................................................... done, booting the kernel.
I bet it does not hang. It's probably just the wrong settings for serial console!
Hi Steven, I debugged the kernel startup. It hanged because the architecture number (508) did not match the sbc9328 ID. I temporarily changed it in U-Boot platform-specific file and the kernel completes the first stage. Now it hangs in console_init function when it tries to initialize the 8250 serial driver. Why is this driver enabled? Can I safely remove it from configuration?
Regards,
llandre
DAVE Electronics System House - R&D Department www.dave-tech.it
participants (2)
-
llandre -
Steven Scholz