TK1 flash os problem >download command failed NvError 0x120002

on my design TK1 board ,but i flash os is failed.

use command :./flash.sh jetson-tk1 mmcblk0p1
and use jetpack tool the result as same

Nvflash 4.13.0000 started
BR_CID: 0x340010017410c1060800000019fd0380
rcm version 0X400001
Skipping BoardID read at miniloader level
System Information:
chip name: unknown
chip id: 0x40 major: 1 minor: 1
chip sku: 0x0
chip uid: 0x000000017410c1060800000019fd0380
macrovision: disabled
hdcp: disabled
jtag: disabled
sbk burned: false
board id: 0
warranty fuse: 0
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0

RCM communication completed
BCT sent successfully
sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb

  • 59661/59661 bytes sent
    tegra124-jetson_tk1-pm375-000-c00-00.dtb sent successfully
    odm data: 0x6009c000
    downloading bootloader – load address: 0x83d88000 entry point: 0x83d88000
    download command failed NvError 0x120002
    command failure/warning: bootloader download failed (bad data)

Failed flashing ardbeg.

what should i do?
thanks .

0x120002 is:

0x00120002, "packet was nacked")

Are you using a VM to flash? If so, this is probably the cause. If not, then it will still be USB related.

hi linuxdev,
thanks for your reply.
i use host for ubuntu 16.04.
usb what’s the problem? and Is there any relationship with board id? or modify jetson-tk1.conf will be flash os.This problem is really troublesome.

I am rewriting the system on a systematic TK1,the tk1 design by other company.and it may be that the problem is not usb related.Are there any other good ideas?

For a custom board there can be a board id issue. Someone who has worked on custom boards would have to suggest how to correct this in such a case.

Thanks.

Can you tell me what is the role of board id?

I couldn’t tell you the exact role. Each SoC has different hardware surrounding it, and different device trees associated. The flash.sh app picks and chooses some of the boot time files to apply to the flash based on arguments, e.g., different extlinux.conf. I suspect that the board id helps pick some of the other partition content which depends on the hardware surrounding the SoC.

In this case.Do you have any good Suggest? I don’t flash os on the tk1.

Someone from NVIDIA could tell you more about how the device ID from flash is determined, along with what changes when it is a custom board. I have not personally been in a situation to use a custom ID.

I will check this, but I doubt how other users who are on customized board escaped similar issue.
Could you describe more about your design?

Hi 156951135,

Any information can be shared?

Thanks

Hi kayccc
What information do you need?

Hi WayneWWW
Thanks for you reply,this board is not our company, so I do not have more description.

We had similar error before, but all of them have different cause. Some are hardware issues.
So it would be better to check your hardware design first.