i.MX6ul is not flashing using imx_uart

[mkonnov]

I'm struggling with downloading u-boot using imx_uart.

I'm using the following command when trying to flash the reference u-boot image

imx_uart -n /dev/ttyUSB0 /usr/etc/imx-loader.d/mx6ull_usb_work.conf /opt/boqpod/gsmbox_firmware/misc/ccimx6ulsbc-installer/u-boot-ccimx6ulsbc1GB.imx

I have no RTC/CTS lines connected, so I'm using '-n' option.

Nevertheless, I'm not sure if I'm doing everything correctly.

Step-by-step.

1. I'm launching the command

imx_uart -n /dev/ttyUSB0 /usr/etc/imx-loader.d/mx6ull_usb_work.conf /opt/boqpod/gsmbox_firmware/misc/ccimx6ulsbc-installer/u-boot-ccimx6ulsbc1GB.imx

and see the following output

config file </usr/etc/imx-loader.d//mx6ull_usb_work.conf>
parse /usr/etc/imx-loader.d//mx6ull_usb_work.conf
starting associating phase..........

and it fails if the reset button is not pressed.

2. Once the button is pressed again, the response is seen

association phase succeeded, response was 0x23454523

... and it stalls until I press the reset again.

3. After I'm pressing the reset again, I see the following

HAB security state: development mode (0x0a0d0a0d)
== work item
filename /opt/boqpod/gsmbox_firmware/misc/ccimx6ulsbc-installer/u-boot-ccimx6ulsbc1GB.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

<<<520, 520 bytes>>>
failed (security 0x74206361, status 0x7573653a)
clear dcd_ptr=0x877ff42c

loading binary file(/opt/boqpod/gsmbox_firmware/misc/ccimx6ulsbc-installer/u-boot-ccimx6ulsbc1GB.imx) to 877ff400, skip=0, fsize=b1c00 type=aa

It takes 1 minute to 'load' the binary and that's what I see in the end

<<<728064, 728064 bytes>>>
failed (security 0x07070707, status 0x07070707)
jumping to 0x877ff400
failed (security 0x07070707, status 0x07070707)

Could somebody please explain if I'm doing smth wrong and how to flash the binary properly.

Best regards.

[maa-x]

I have the same exact issue. Unclear how to progress. HAB is not enabled on the device.

[mkonnov]

@MaxIsMyName so have you overcame the problem ?