Bring up issue on i.MX6solo based custom hardware.

[shabeerbadarudh]

Hi All,
Our  custom "u-boot.imx" is not booting at all if we use mfg tool for loading images. But the corresponding "uboot" elf file booting successfully if it loads to DDR using lauterbach.

Also there is a strange behavior while run the DDR calibration utility.
If we run the calibration tool , it gives some success messages and shows the calibrated values. But if we run the test by put the HID jumpers( the jumpers put on boot mode gpio pins on our hardware for setting HID mode manually), calibration utility getting hanged.

The similler behavior is getting while run the mfgtool also.
That is without HID jumper if we run mfgtool, pop up windows shows the messages for loding u-boot, kernel,dtb etc. then "Jumping to OS" message and no more message after that and also no logs on the serial terminal.
But if we run mfgtool with HID jumper, just u-boot loading pop up message is shown then there is no more messages.

Please let us know any suggestion for resolve the issue. 

Our system details:
SOC: i.MX6Solo
DDR: IS21ES08G
U-boot - 2015.04
Kernel - 4.1.15

Thanks in Advance,

Shabeer.

[igorpadykov]

Hi Shabeer

""Jumping to OS" message and no more message" may be caused

by reason that mfg tool was designed for i.MX6 NXP Sabre reference boards.

For new board (or processor) recommended to run ddr test and update Mfg Tool firmware
image with new ddr calibration coefficients found from test
https://community.nxp.com/docs/DOC-105652
Update coefficients in uboot/../mx6sabresd/mx6solo_4x_mt41j128.cfg and
rebuild Mfg Tool firmware (files in  ../firmware folder, fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot).
Also refer to p.14 i.MX_6Dual6Quad_SABRE-SD_Linux_User's_Guide.pdf - it shows in more details
which files are used by Mfg Tool.
For rebuilding use sect.6.2 Manufacturing Tool, MFGTool attached Yocto Guide.
Please use NXP Linux repository:
https://source.codeaurora.org/external/imx/linux-imx/tree

For jumpers suggest to check custom board schematic with Sabre board:

Schematics (1)
i.MX6_SABRE_SDP_DESIGNFILES
http://www.nxp.com/products/software-and-tools/hardware-development-tools/sabre-development-system/s...

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

[shabeerbadarudh]

Hi Igor,

Thanks for the response. 

I forgot to update about DCD values in previous post. I have already updated DCD values and created new u-boot for our hardware and it is used for loading using JTAG. and for the "initramfs" image we have just used
one which got from mfgtool(This initramfs  was worked with some of other custom hardware before).

So my query is, do we want to create a new initramfs (fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot) for the new target hardware?. If yes let me know what modifications are need to do in initramfs with respect to Eval board. Please share any documents are available.

Thanks in Anvance,

Shabeer

[igorpadykov]

Hi Shabeer

>do we want to create a new initramfs (fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot) for the new target hardware?.

yes, if "one which got from mfgtool" is not working.

Modifications and documentation are described in my first answer.

Best regards
igor

[shabeerbadarudh]

Hi Igor,

Thanks for the response. I will try with new initramfs. 

Thanks and regards,

Shabeer

[shabeerbadarudh]

Hi Igor,

Still now we don't  have luck on bring up the board.
Since the mfg u-boot is not even up through usb interface, we are looking into u-boot.
We were able to load the both "u-boot" elf and bin files using lauterbach, but the corresponding u-boot.imx is not loading through mfgtool/usb_loader utility. Attached image is the screen shot while run the "imx-usb" utility,
the log shows both DCD and u-boot images are loading into IRAM and DDR. But while check the DDR location 0x17800000(using lauterbach), the memory contents are not expected one and seems like the data is not successfully loaded into DDR. Please let me know the reason for this strange behavior or can you guide us to resolve this problem?

Thanks in Advance,
Shabeer

[shabeerbadarudh]

Hi ,

I am facing issues to attach the file. Please find below the logs....

shabeer@ubundu-OptiPlex-3020:~/SecureGateway/imx_loader/imx_usb_loader$ sudo ./imx_usb u-boot.imx
config file <.//imx_usb.conf>
vid=0x066f pid=0x3780 file_name=mx23_usb_work.conf
vid=0x15a2 pid=0x004f file_name=mx28_usb_work.conf
vid=0x15a2 pid=0x0052 file_name=mx50_usb_work.conf
vid=0x15a2 pid=0x0054 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0061 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0063 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0071 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x007d file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0080 file_name=mx6ull_usb_work.conf
vid=0x1fc9 pid=0x0128 file_name=mx6_usb_work.conf
vid=0x15a2 pid=0x0076 file_name=mx7_usb_work.conf
vid=0x1fc9 pid=0x0126 file_name=mx7ulp_usb_work.conf
vid=0x15a2 pid=0x0041 file_name=mx51_usb_work.conf
vid=0x15a2 pid=0x004e file_name=mx53_usb_work.conf
vid=0x15a2 pid=0x006a file_name=vybrid_usb_work.conf
vid=0x066f pid=0x37ff file_name=linux_gadget.conf
vid=0x1b67 pid=0x4fff file_name=mx6_usb_sdp_spl.conf
vid=0x0525 pid=0xb4a4 file_name=mx6_usb_sdp_spl.conf
vid=0x1fc9 pid=0x012b file_name=mx8mq_usb_work.conf
config file <.//mx6_usb_work.conf>
parse .//mx6_usb_work.conf
Trying to open device vid=0x15a2 pid=0x0061
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename u-boot.imx
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 3
jump_addr 0x00000000
== end work item
loading DCD table @0x910000

<<<552, 552 bytes>>>
succeeded (security 0x56787856, status 0x128a8a12)
clear dcd_ptr=0x177ff42c

loading binary file(u-boot.imx) to 177ff400, skip=0, fsize=30c00 type=aa

<<<199680, 199680 bytes>>>
succeeded (security 0x56787856, status 0x88888888)
jumping to 0x177ff400