Hi,
We have a customized Tegra K1 SOC board which is same as jetson tk1 and we are facing issues in bring it up.I would like to know the significance of DTB file downloading during nvflash. Will it be parsed and some initialization will be done before “fastboot.bin” is downloaded and jumped for execution? Please find the attached logs regarding the issue we are facing .
Any help would be really appreciated
Debug_logs.txt (3.48 KB)
I have the same problem like you
I have no idea about this question
customized BOARD (K1 version：575M)
$ lsusb
Bus 001 Device 023: ID 0955:7740 NVidia Corp.
$ sudo ./flash.sh -S 14580MiB -r jetson-tk1 mmcblk0p1
…
RCM communication completed
BCT sent successfully
sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb
RS232 info
[0000.000] [TegraBoot] (version UNDEF_BUILD)
[0000.004] Reset reason: power on reset
[0000.007] Processing in recovery mode
[0000.011] Established communication link with host
[0000.054] Downloaded bct successfully
[0000.058] No Battery Present
[0000.062] Sdram initialization is successful
[0000.073] Downloaded DTB successfully
[0000.099] Unsupported Platform 0xffff
[0000.103] populate platform details failed with error 0x2 in DownloadBootloade
[0000.111] Downloading Bootloader failed with 0x2
[0000.116] Download Bootloader failed with error 0x2 in NvTbootServer func at 1
[0000.124] Error is 2
Nvidia TK1 BOARD (K1 version：580M)
lsusb
Bus 001 Device 028: ID 0955:7140 NVidia Corp.
$ sudo ./flash.sh -S 14580MiB -r jetson-tk1 mmcblk0p1
…
RCM communication completed
BCT sent successfully
sending file: tegra124-jetson_tk1-pm375-000-c00-00.dtb
RS232 info
[0000.000] [TegraBoot] (version UNDEF_BUILD)
[0000.004] Reset reason: power on reset
[0000.008] Processing in recovery mode
[0000.011] Established communication link with host
[0000.045] Downloaded bct successfully
[0000.049] No Battery Present
[0000.053] Sdram initialization is successful
[0000.064] Downloaded DTB successfully
[0000.091] No Battery Present
[0000.169] Downloaded bootloader successfully
[0000.173] CPU-bootloader entry address: 0x83d88000
[0000.177] BoardId: 375
[0000.180] Vpr Carveout Base=0x0f4600000 Size=0x00ba00000
[0000.185] Tsec Carveout Base=0x0f2600000 Size=0x002000000
[0000.190] Lp0 Carveout Base=0x0f25ff000 Size=0x000001000
[0000.195] Xusb Carveout Base=0x0f2300000 Size=0x000200000
[0000.200] Platform-DebugCarveout: 0
[0000.227] CPU power rail is up
[0000.230] Performing RAM repair
[0000.233] CPU clock init successful
Hi ,
At present i don’t have debug interface for UART 4, hence not able to capture the logs.But from your logs, i could see that PID and VID of USB(NVIDIA usb recovery mode) have different product id’s which matches my observations also.
At my end i see the following lsusb logs
“Bus 002 Device 023: ID 0955:7340 NVidia Corp.” – In your case "Bus 001 Device 023: ID 0955:7740 NVidia Corp. "
The only difference i could see is “Unsupported Platform 0xffff” and i am not sure this is because of this PID difference or board ID difference . In my case board ID matches with the Jetson. Can you confirm at your end.
Hi ,
In my case i made some progress. In our case custom board Board ID ROM component is missing.
At your side i am suspecting that EEPROM data is 0xffff and is not matching with Board ID , hence the error “Unsupported Platform 0xffff”. Writing the valid data to the EEPROM might solve the issue.
Please let me know if you found out any other issue/ progress.
thanks saiprasad3103
My board has EEPROM, but did not write any value.
I will try your results.
I thought it was tegra124-jetson_tk1-pm375-000-c00-00.dtb This file does not correct today.
Modified files tegra124-jetson_tk1-pm375-000-c00-00.dtb into nvidia TK1 board, boot normally.
As a result, this file does not cause this problem.
Hi ,
Also it looks like in your case EEPROM depth is more and it requires more than one cycle for addressing. Where as in case of Jetson , it is usually one cycle for addressing .