AnsweredAssumed Answered

Recover from an erased uboot image in closed mode

Question asked by Jorge Fernandez on May 8, 2015
Latest reply on Sep 18, 2017 by Evgeny Molchanov

Hi,

 

I have a custom imx6q board with the uboot in a SPI memory. I've saved a signed version of the uboot

in the SPI and the boot is ok. Then I've set the SRK, and I've set the closed mode to have a secured environment.

I can boot ok.

 

Then I wanted to test how to recover from an error in the SPI memory. Then I've erase the memory

the same way I've done to save the uboot other times. I expect to have the serial download mode

available to do that. I reset the board and I can see the message

 

# lsusb

Bus 002 Device 054: ID 15a2:0054 Freescale Semiconductor, Inc. i.MX6Q SystemOnChip in RecoveryMode

 

but when I try to send the same uboot signed image with the imx_usb_loader tool I get error an no uboot console appears:

 

# ./imx_usb u-boot-signed.imx

parse mx6_usb_work.conf

15a2:0054(mx6_qsb) bConfigurationValue =1

Interface 0 claimed

report 1, wrote 16 bytes, err=0

report 3, read 4 bytes, err=0

read=12 34 34 12

u-boot-signed.imx 0 0 1 0 1 2

main dcd length 2f8

sub dcd length 2f4

w3 in err=-7, last_trans=0  00 00 00 00

addr=0x021b001c, val=0x04088032

w4 in err=-7, last_trans=0  00 00 00 00

dcd_ptr=0x177ff42c

!!perform_dcd returned -7

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

report 1, wrote 0 bytes, err=-7

report 3, read 0 bytes, err=-7

read=00 00 00 00

4 in err=-7, last_trans=0  00 00 00 00

 

Is there some way to recover or I have to reprogram the SPI memory in other board?

 

Regards

Outcomes