Hi.
I hope someone can open my eyes on this. We try to port our MX27 board to the new u-boot loader using the SPL code rather then the self hacked NAND->SDRAM.
I'm not able to get anything run. The console stays dead.
Let start here: To see if the second image is booting I tried to load the image using TFTP and memcpy/memcmp it to the TEXT_BASE (0xa7800000) and go. The u-boot-v2 is loaded at 0xa7f00000.
U-Boot 2.0.0-rc9-00188-geb5172d-dirty (Mar 24 2011 - 12:59:07) Board: MX27 NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 592 at 0x04a00000 dm9000 i/o: 0xd4000000, id: 0x90000a46 got MAC address from EEPROM: 00:00:00:00:00:00 Using environment in NAND Flash chip id: [2,882,1,01d] mpll: 398999390 Hz spll: 239999725 Hz arm: 265999593 Hz perclk1: 66499898 Hz perclk2: 66499898 Hz perclk3: 66499898 Hz perclk4: 66499898 Hz clkin26: 26000000 Hz ahb: 132999796 Hz ipg: 66499898 Hz Malloc space: 0xa6f00000 -> 0xa7f00000 (size 16 MB) Stack space : 0xa6ef8000 -> 0xa6f00000 (size 32 kB) running /env/bin/init...
uboot:/ tftp u-boot.bin /dev/ram0 phy0: Link is up - 100/Full TFTP from server 10.128.2.105; our IP address is 10.128.2.10 Filename 'u-boot.bin'. Loading: ########################################## done Bytes transferred = 211308 (3396c hex) uboot:/ memcpy -s /dev/ram0 0 0xa7800000 211308 uboot:/ memcmp -s /dev/ram0 0 0xa7800000 211308 OK uboot:/ go 0xa7800000 ## Starting application at 0xA7800000 ...
System.map a7800000 T __image_copy_start a7800000 T _start a7800020 t _undefined_instruction a7800024 t _software_interrupt a7800028 t _prefetch_abort a780002c t _data_abort a7800030 t _not_used a7800034 t _irq a7800038 t _fiq ...
Any Idea?
Chris