We are developing from scratch our board
U-BOOT 2017.01 (MAR 30 2017 – 17:48:18)
CPU: Freescale i.MX23 rev 1.4 AT 454 MHZ
Boot: SSP SD/MCC#0
DRAM: 64MiB
MMC: MXS MMC: 0
*** Warning – bad CRC, USING DEFAULT ENVIROMENT
IN: serial
OUT: serial
ERR: serial
NET: net initialization skip
Not Ethernet found
Hit any key to stop autoboot: 3
Hit any key to stop autoboot: 0
=>
Our question is: “Why the boot process is stopped?” because in the development board the same SD card give us the following output
Hit any key to stop autoboot: 3
Hit any key to stop autoboot: 2
Hit any key to stop autoboot: 1
Hit any key to stop autoboot: 0 (why in our board jump from 3 to 0 so fast)
Switch to partitions #0, OK
MMC0 is current device
Reading boot.scr
**unable to read file boot.scr**
Reading uimage
1421336 bytes read in 454 ms (3 MiB – s)
Booting from MMC …
Reading imx23-olinuxino.dtb
10554 bytes read in 27 ms (380.9 KiB – s)
##booting kernel from legacy image at 42000000 …
Image name: ARM Openwrt linux 3.18.44
Image type: Linux Kernel image (uncompress)
Data size 1421272 bytes = 1.4 MiB
Load address 40008000
Entry point: 40008000
There find checksum…
Ok
##Flatting device tree blob at 41000000
Booting using the FDT BLOB at 0X41000000
Loading kernel image…
Ok
Loading device tree to 43b62000,end 43b67939…
Ok
Starting kernel
Booting linux on fisical CPU X0X
Linux version 3.1844
Messages continue until the boot process end
We run the memory test successfully with the following messages
Memory read stop - non error reports, memory test is successfully finish
Uncompressing Linux................
done, booting the kernel
Now I want to generate u-boot with openwrt
I appreciate any advice
Best Regards
Sergio
Thanks for your response Igor
I found another solution from someone in the forum and he suggest
Change de frequency to 96MHZ In boot_prep/init.c, uncomment the #define EMI_96M to enable this
What do you thing abount this solution?
Regards
Sergio
This is usually indicative of a DDR problem.
The above message indicates you're using init_ddr_mt46v32m16_133Mhz - is this the DDR1 part on your board?
It is possible to run at 96MHz. In boot_prep/init.c, uncomment the #define EMI_96M to enable this. Suggest you try this and see if you can get the kernel uncompressed.
Útil Sí • NoMe gusta • Mostrar 0 me gusta0Responder
sure I,m using Micron DDR MT46V32M16
I changed the frequency to 96MHz and boot Linux successfully.
The thing is, I designed a 4 layer low cost board, so I compromised the EMI a little bit; seems I'm paying for that :-)
Thank you all
Hi Sergio
changing the frequency to 96MHz may help,
but does not guarantee that ddr will work fine in all use cases/conditions.
Best regards
igor
Hi Sergio
SD card for development board may not work on custom board due to possible ddr errors,
please try to test memory and rebuild image for custom board
https://community.nxp.com/message/481403?commentID=481403#comment-481403
i.MX28 DDR stress test | NXP Community
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
We found the following information in www.olimex.com
Development board use RAM 46V32M16-5V REV F (out of production) but we have 46V32M16-5V REV J and Olimex confirm the board does not work with this version
How can we resolve this issue?