sb_loader error(-13) during download

[jrrguzman]

Hi everyone,

I'm developing a new board based on the IMX287.

I'm trying to load the u-boot from the KARO startekit-5 V3 (my design is based in this board) with the provided sb_loader executable and I get the following output:

Looking for a STMP HID device for 10 seconds...

  Found USB#VID_15A2&PID_004F#7&2EE36394&0&3.

Downloading uboot.bin to device.

  .  Error(-13) during download.

Quitting.

Does anyone know what I am doing wrong? Any clue about that error?

Kind regards

[igorpadykov]

Hi Javier

sb_loader needs *.sb file (generated by elftosb utility), for example:

sb_loader.exe /f imx28_uboot.sb

please check sect.5.3.1 USB Boot attached doc.

IMX_ELFTOSB_TOOL: Tool to convert ELF format executable files and other source files

into the encrypted boot images used by the i.MX23 and i.MX28. Includes Windows

and Linux binaries, full source code, and all related documentation.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

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

-----------------------------------------------------------------------------------------------------------------------

[jrrguzman]

Hi Igor,

This is how I call sb_loader:

>sb_loader.exe /F uboot.bin

Looking for a STMP HID device for 10 seconds...

  Found USB#VID_15A2&PID_004F#7&2EE36394&0&3.

Downloading uboot.bin to device.

  .  Error(-13) during download.

Quitting.

When I try to load the image in the KARO board, it works without problems. But I can't make it work with my own board.

I'll try with the .sb extension but I don't think I'll get anything different.

[igorpadykov]

Hi Javier

I think you should check how generated karo uboot.bin

elftosb can generate encrypted and not encrypted image, this depends

what fuses are blown on chip. You can compare fuses on KARO board

with own using IMX_OBDS   (running stmp_otp.c example with jtag).

The output boot image is by default not encrypted. To encrypt the boot image

you need to provide one or more keys. Use the -z switch to add a

key that consists of all zeroes. This is the default state of the hardware key in

a chip that has not yet had its OTP key burned.

~igor