Hi Greg, many thanks. I verified the following:
1. objdump output m68k-uclinux-objdump --headers linux-2.6.x/vmlinux linux-2.6.x/vmlinux: file format elf32-m68k Sections: Idx Name Size VMA LMA File off Algn 0 .text 0016e2e0 00020000 00020000 00002000 2**4 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .data 00011d20 0018e2e0 0018e2e0 001702e0 2**4 CONTENTS, ALLOC, LOAD, DATA 2 .init.text 0000cbb6 001a0000 001a0000 00182000 2**2 CONTENTS, ALLOC, LOAD, READONLY, CODE 3 .init.data 00001448 001acbb8 001acbb8 0018ebb8 2**2 CONTENTS, ALLOC, LOAD, DATA 4 .bss 0000b724 001ae000 001ae000 00190000 2**4 ALLOC 5 .debug_line 000d72fe 00000000 00000000 00190000 2**0 CONTENTS, READONLY, DEBUGGING 6 .debug_info 00d1cd6d 00000000 00000000 002672fe 2**0 CONTENTS, READONLY, DEBUGGING 7 .debug_abbrev 0007e1a6 00000000 00000000 00f8406b 2**0 CONTENTS, READONLY, DEBUGGING 8 .debug_aranges 000049a0 00000000 00000000 01002218 2**3 CONTENTS, READONLY, DEBUGGING 9 .comment 000020b2 00000000 00000000 01006bb8 2**0 CONTENTS, READONLY 10 .debug_pubnames 0001a852 00000000 00000000 01008c6a 2**0 CONTENTS, READONLY, DEBUGGING 11 .debug_frame 00048e4c 00000000 00000000 010234bc 2**2 CONTENTS, READONLY, DEBUGGING 12 .debug_str 000549d4 00000000 00000000 0106c308 2**0 CONTENTS, READONLY, DEBUGGING 13 .debug_loc 0015b9e6 00000000 00000000 010c0cdc 2**0 CONTENTS, READONLY, DEBUGGING 14 .debug_ranges 00041170 00000000 00000000 0121c6c2 2**0 CONTENTS, READONLY, DEBUGGING angelo@angel7:~/sysam/amcore/uClinux-dist$ seems to be correct, even if i am not 100% sure, maybe you can confirm this. 2. bytes in the nor flash before copying, comparing with bytes loaded in sdram amcore$ md ffc20000 20 ffc20000: 4e7146fc 27002e7c 00000000 4e7bf801 NqF.'..|....N{.. ffc20010: 23cf0018 e2e42e7c 00000000 23cf0018 #......|....#... ffc20020: e2e0203c 01000000 d08f23c0 0018e2ec .. <......#..... ffc20030: 203c0100 00004e7b 00024e71 203c0000 <....N{..Nq <.. ffc20040: c0204e7b 00047000 4e7b0005 203ca000 . N{..p.N{.. <.. ffc20050: 02004e7b 00024e71 41f9001a e00043f9 ..N{..NqA.....C. ffc20060: 001b9724 24482028 00085080 0280ffff ...$$H (..P..... ffc20070: fffcd1c0 d3c023c9 0018e2e8 20202300 ......#..... #. amcore$ md 20000 20 00020000: 4e7146fc 27002e7c 00000000 4e7bf801 NqF.'..|....N{.. 00020010: 23cf0018 e2e42e7c 00000000 23cf0018 #......|....#... 00020020: e2e0203c 01000000 d08f23c0 0018e2ec .. <......#..... 00020030: 203c0100 00004e7b 00024e71 203c0000 <....N{..Nq <.. 00020040: c0204e7b 00047000 4e7b0005 203ca000 . N{..p.N{.. <.. 00020050: 02004e7b 00024e71 41f9001a e00043f9 ..N{..NqA.....C. 00020060: 001b9724 24482028 00085080 0280ffff ...$$H (..P..... 00020070: fffcd1c0 d3c023c9 0018e2e8 20202300 ......#..... #. amcore$ no issues detected, copy works fine, and sdram has been hardly tested for proper working. 3. console, boot args seems the same as before, where using "colilo" kernel was loaded correctly: [ ] 8250/16550 and compatible serial support *** Non-8250 serial port support *** [*] Coldfire serial support (115200) Default baudrate for Coldfire serial ports [*] Coldfire serial console support [ ] Support for timberdale UART [ ] Altera JTAG UART support [ ] Altera UART support I afraid the kernel is stucked somewhere before the serial console initialization. Hope for some other suggestions, many thanks angelo On 02/08/2011 13:57, Greg Ungerer wrote: > Hi Angelo, > > On 08/02/2011 06:33 PM, angelo wrote: >> i am looking for some help for the following issue: >> >> I had uClinux running perfectly on Coldfire MCF5307/4M nor FLASH/16M >> SDRAM, when it was copied from flash to SDRAM at address 0x400, just >> after the VBR, and i was then jumping at 0x400 from the "colilo" >> bootloader that was running from the flash. >> >> Now i changed the bootloader using U-boot, and this bootloader works >> reloacted into SDRAM, from 0x0 to 0x20000, so i recompiled uClinux to be >> copied in SDRAM just after the bootloader, with these settings: >> >> (0x0) Address of the base of RAM >> (0x1000000) Size of RAM (in bytes), or 0 for automatic >> (0x0) Address of the base of system vectors >> (0x20000) Address of the base of kernel code > > Firstly check that these settings are getting it right by > objdump'ing the kernel object headers: > > m68k-uclinux-objdump --headers linux-2.6.x/vmlinux > > >> Once copied from flash to sdram (at 0x20000) and started (with u-boot >> command "go 0x20000") i don't get any output from the serial console at >> all, like if the kernel is locked near the beginning. > > Double check that the code you copied really is what you think > it is. Dump a few dozen bytes from 0x20000 in uboot and compare > against the image.bin/kernel you loaded. > > >> I don't know how to debug this issue, any help is very appreciated. > > Is it possible that the kernel is running, but just that the console > is no longer being set properly (say by not getting bootargs correctly)? > > Regards > Greg > > > ------------------------------------------------------------------------ > Greg Ungerer -- Principal Engineer EMAIL: g...@snapgear.com > SnapGear Group, McAfee PHONE: +61 7 3435 2888 > 8 Gardner Close, FAX: +61 7 3891 3630 > Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev