I want to pre-flash the u-boot env vars, so I dump the the env vars with this command:
sudo dd if=/dev/mmcblk0boot1 of=ubenv.bin bs=32k count=1 skip=123
This works for Jetson Nano modules.
In the flash.xml the following parameters added for UBENV partition:
The start offset is 0x7D8000, but the u-boot actually saves the environment variables at 0x7FE000 absolute address (0x3FE000 in /dev/mmcblk0boot1).
This address is out of range defined in the flash.xml.
How can I fix this problem?
I think it should save the data at 0x7D8000 as the Nano module does.
I see the CONFIG_ENV_OFFSET=0xFFFFE000 in the p3636-0001_defconfig.
Maybe this cause the problem.
I can fix this in the r32.6.1 u-boot source, and I can recompile.
Does the FDT work in this source with TX2 NX?
If it is not, how can I fix the “silence panic” problem in the source?
A source patch file would have been better than binary upload.
I cannot answer what you really want to know, but understand you referenced a link to a TX2 solution. The TX2 uses U-Boot, but the NX does not have U-Boot. Both platforms have CBoot, but on the TX2 CBoot chain loads into U-Boot. The NX directly loads the kernel from CBoot without using U-Boot, so configuration of environment will differ (although I suppose it is possible someone abstracted the “.conf” files related to this to a point where changes could appear the same…don’t know).
I know anything Xavier does not use U-Boot. Is there a difference in how CBoot and U-Boot are used in the TX2 NX as compared to the TX2 full dev kit on the larger carrier board? I’m just wondering if the different TX2 variants sometimes use U-Boot, but sometimes do not. My thought was that all TX2 variants do not use U-Boot. Then again, since CBoot has inherited some of the U-Boot functionality I suppose that even without U-Boot there might be cases where CBoot has similar bugs.