Hi,
I have build custom board with imx6 dual and ddr2 memory, and I have build u-boot with memory calibration from ddr stress tool. I can load u-boot.imx with sb_loader.exe into target memory and run it. I see led is turning ON on the board.
Problem is that I can not load u-boot.imx with mfg tool. When loading u-boot mfgtool stops and stays in that position infinite time without error. It seems that u-boot somehow blocks mfgtool. How is that possible?
What I am doing wrong?
Please help!
Thanks, regards, Ivan Ljubicic.
Hi Ivan
typical uboot images in MFG2 Tool folder are images with offset -
written for programming on external boot devices. For usb
load one needs the same images, but without offset. Just for example
attached u-boot-mx6q-sabresd.bin - original Uboot image found in MFG2
package (..\Profiles\MX6Q Linux Update\OS Firmware).
u-boot-mx6q-sabresd_nopad.bin - the same image without offset.
One can use modified ucl2.xml u-boot-mx6q-sabresd_nopad.bin is Uboot image
without offset (0x400). Modified "SabreSD-SD" profile, tested with
Mfgtools-Rel-L3.0.35_1.0.1_MX6Q_UPDATER:
<LIST name="SabreSD-SD" desc="USB SDP">
<CMD state="BootStrap" type="boot" body="BootStrap" file ="u-boot-mx6q-sabresd_nopad.bin" >Loading image</CMD>
<CMD state="BootStrap" type="jump" > Jumping to image. </CMD>
<CMD state="Updater" type="push" body="$ echo Load Complete!">Done</CMD>
</LIST>
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi Igor,
I have done:
dd if=u-boot.bin of=u-boot-nopad.bin bs=1024 skip=1
and try to load with mfgtool2, but I have the same problem ant it is
only with bin file with valid DDR calibration configuration. If I use
non valid DDR configuration file Mfg-tool pass on with execution to
uImage and initramfs.cpio.gz.uboot but fails on jump because of memory.
sb_loader that comes with mfgtool fails to load good memory calibrated
bin file, but with version sb-loader 1.2 I can load such image to memory
and run it.
Why sb_loader version 1.2 can load image to memory and all other tools
can not.? I am not clear what I am missing.
Thanks, regards, Ivan.
Hi Ivan
what board is used for image building, strictly speaking
mfg tools was tested only with nxp reference boards,
please refer to Yocto Guide sect.5.1 Build configurations.
Sources of uboot and linux at:
http://git.freescale.com/git/cgit.cgi/imx/uboot-imx.git/tree/?h=imx_v2015.04_4.1.15_1.0.0_ga
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/?h=imx_4.1.15_1.0.0_ga
If image is built for other board, usually it is supported by community
difference between Yocto Community BSP and Free... | NXP Community
Such builds were not tested with mfg tools, however they probably will work
fine with sb_loader and other customized for such purposes tools.
Also such boards usually use u-boot-fslc uboot, not nxp uboot-imx and there
may be differencies between them.
sb_loader is not officially supported tool for i.MX6 processor, so seems proper way
to post that on
https://lists.yoctoproject.org/listinfo/meta-freescale
Best regards
igor
Hi Igor,
I have managed to fix problem. It was with config memory in
400mhz_2x512mx32.cfg file.
Count of
DATA 4, address, value
must be under 128 commands. If it is over sb_loader from mfg tool will
report memory problem. So I can now load uboot and start it over
mfgtool. But problem is now to load uImage and initramfs.cpio.gz.uboot.
uImage I have created from zImage with following command:
mkimage -A arm -O linux -T kernel -C none -a 0x0 -e 0x0 -n "Linux
kernel" -d zImage uImage
and
initramfs.cpio.gz.uboot
I have build with: bitbake fsl-image-mfgtool-initramfs
Can I use those files how I created them or there is another option?
Thanks, regards, Ivan Ljubicic.