I have R35.4.1 building on a VM running Ubuntu 20.04. I’m trying to flash it to our custom AGX Orin board. It progresses for a while as in the attached flash log, but it dies before actually completing the write to flash:
Traceback (most recent call last): File “/home/cread/uCORE/Linux_for_Tegra/bootloader/tegraflash_impl_t234.py”, line 1401, in tegraflash_update_bpmp_dtb if bpmp_dtb == None and bpmp_dtb_in_layout == None: UnboundLocalError: local variable ‘bpmp_dtb’ referenced before assignment
The script I used to flash the system is:
export ODMDATA=“gbe-uphy-config-0,nvhs-uphy-config-0,hsio-uphy-config-16”
export PINMUX_CONFIG=“Orin-p0760-a101-pinmux.dtsi”
export DTBFILE=tegra234-p3701-0004-p0760-a101.dtb
./flash.sh p0760-a101+p3701-0000 mmcblk0p1 |& tee -a $LOG_FILE
I have uploaded the full log of the flash operation as well as the configuration files (with added .txt suffix).
I have looked at two other posts that reference this error, but neither was helpful in diagnosing my issue.
It appears that the BPFDTB_FILE parameter was set to a non-existent file. I set it to one based on the AGX Orin DevKit, p3737, and now it writes to the SOM.
Questions:
Is that the correct approach, or should I create a *-bpmp-*.dtb device tree blob for my custom board?
If I need to create one, is there source for the p3737 blob that I can tweak for my board?
If I must use the p3737 blob, then shouldn’t its name not be specific to the DevKit?
I have done something (described in my Sep 10 post) that seems to have gotten writing to the SOM working, but I don’t know if that was the right thing to do.
My last response to DavidDDD’s questions went unanswered. I’m still looking for how to generate/find the correct BPFDTB_FILE or bpmp_dtb for our custom board and would appreciate guidance.
Hi,
It looks like your SKU is 0004. Could you tell me where the BPFDTB_FILE=“tegra234-bpmp-3701-0004-0760-a101.dtb” is located?
It should normally be under the ./bootloader directory.
I don’t have a file named tegra234-bpmp-3701-0004-0760-a101.dtb anywhere. The BPFDTB_FILE variable is set in the file p0760-a101+p3701-0000.conf to one of the following:
because I didn’t see any info on creating the -bpmp- version of the .dtb file for our custom board. So, I just used the -bpmp- file from the DevKit. Do the flashing scripts create the -bpmp- .dtb files? Is there an alternative way to create them?
I don’t have a result. I’m still hoping to be told
Whether it’s important to have a BPFDTB_FILE, i.e. a -bpmp- version of a device tree blob, that’s custom to our board, or not. We’re currently using ones for the DevKit.
If it is important, how do I create one. I haven’t seen anything indicating how to create that kind of file.