Hi supporters,
I want to set prod-setting in bootloader as in this page Common Prod Configuration — NVIDIA Jetson Linux Developer Guide . Here is what I did:
- Create a prod-setting file Linux_for_Tegra\bootloader\generic\BCT\aibp0016pbba-mb1-bct-prod.dts with the following content:
/dts-v1/;
/ {
/* Placeholder currently. Data must be populated once available */
prod {
major = <1>;
minor = <0>;
addr-mask-data =
/* SOR */
<0x1380C118 0xFFFFFFFF 0x10101010>;
};
};
-
In board config file, add
PROD_CONFIG=“aibp0016pbba-mb1-bct-prod.dts”; -
Then make a full-flash, error always happens as below
[ 0.1514 ] tegrarcm_v2 --instance 1-8.4.2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
[ 0.1516 ] BL: version 1.4.0.4-t234-54845784-e89ea9bc last_boot_error: 0
[ 0.3078 ] Sending bct_mem
[ 0.3586 ] Sending blob
[ 0.4214 ] ERROR: might be timeout in USB write.
Error: Return value 3
Command tegrarcm_v2 --instance 1-8.4.2 --chip 0x23 0 --pollbl --download bct_mem mem_rcm_sigheader.bct.encrypt --download blob blob.bin
Cleaning up… -
The same error occurs if flash bootloader only
-
The error doesn’t occur if not adding PROD_CONFIG=“aibp0016pbba-mb1-bct-prod.dts”;
-
The error doesn’t occur if adding PROD_CONFIG=“tegra234-mb1-bct-prod-p3767-0000.dts”;, where tegra234-mb1-bct-prod-p3767-0000.dts is original release file in BSP v36.4.3
-
The error occurs if adding PROD_CONFIG=“tegra234-mb1-bct-prod-p3767-0000.dts”; but the content of the file tegra234-mb1-bct-prod-p3767-0000.dts is modified
Without PROD_CONFIG in board config, or with PROD_CONFIG with original prod-settings, the flash succeeded. So, it seems this error is not related to USB transfer signal stability as discussed in this topic ERROR: might be timeout in USB write . I did try to follow the suggestion in that topic, but no help.
Did I miss anything?
Thanks,
Nari