IMX6SL UART 1 stuck after IMX_USB uboot transfer completion

Showing results for 
Search instead for 
Did you mean: 

IMX6SL UART 1 stuck after IMX_USB uboot transfer completion

Contributor I

Hi all,

We have a new IOT gateway based on IMXS6SL with this SOC REVISION :- MCIMX6L8DVN10AB, on which console doesn't come up after we transfer uboot.imx from imx_usb

The task was to bring up uboot on the newer boards. For this, we used, imx_usb utility with uboot binary version :  U-Boot 2014.01-svn219 (Feb 14 2015 - 12:14:31)

Following are the log files:-

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=0x0076 file_name=mx7_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
config file <./mx6_usb_work.conf>
parse ./mx6_usb_work.conf
15a2:0063(mx6_qsb) bConfigurationValue =1
Interface 0 claimed
HAB security state: development mode (0x56787856)
== work item
filename /home/sbhutani/iot/stct_iog1.tar/stct_iog1/bin/imx_images/iog1_uboot
load_size 0 bytes
load_addr 0x00000000
dcd 1
clear_dcd 0
plug 1
jump_mode 2
jump_addr 0x00000000
== end work item
loading DCD table @0x910000

<<<0, 640 bytes>>>
succeeded (status 0x128a8a12)

loading binary file(/home/sbhutani/iot/stct_iog1.tar/stct_iog1/bin/imx_images/iog1_uboot) to 877ff400, skip=0, fsize=32c00 type=aa

<<<207872, 207872 bytes>>>
succeeded (status 0x88888888)
jumping to 0x877ff400
[sbhutani@sudhanshu-bhutani imx_usb_loader-master]$

It says that IMX USB Loader has successfully sent uboot.imx binary with sdp protocol, however, we donot see any Uboot related prints on our console. In summary, there are no logs from uboot, console is not showing anything.

Same imx_usb loader process works well on our older SOC revision: MCIMX6L8DVN10AA, we can see Uboot running in DRAM after imx_usb utility is done with the transfer.

Serial mode gets selected from BOOT_MODE0 and BOOT_MODE1, which is 01 = serial down loader on both the boards. There is no difference in both these boards, except SOC revision.

Can you please suggest, how can we debug this kind of problem. We want to check, whether processor did jumped to RAM location(0x877ff400) for our UBOOT.IMX binary file execution or it is the UART which is not showing the data at all, after uboot is executing.

What HW/SW tools are required on our custom board to triage it further.?

I probed, TX/RX UART with MSO, impedance levels are correct, and it feels, that silicon and PMIC are also coming up. Voltage levels on various modules is also fine.  But, somehow, i don't see any data on TX, when we run the imx_usb utility, there is no execution and no data being on UART.

Can you give us right directions?


Sudhanshu Bhutani

Labels (1)
Tags (1)
0 Kudos
2 Replies

NXP TechSupport
NXP TechSupport

Hi Sudhanshu

had you run ddr test and rebuild uboot (changed *.cfg file with new

calibration settings obtained from test) 

For uart issue one can attach jtag and compare data in ddr (using linker memory map)

with binary uboot file, check uart frequency (set by UARTx_UBMR, (UARTx_UBIR)

CCM_CCGR5 (uart gate).

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

0 Kudos

Contributor I

Thanks, the board was not having correct voltage levels. After replacing fresh chip, it worked

0 Kudos