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?
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.
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.
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.