Hi,
Could you change file one by one and see after changing which files lead to the failure here?
Also, you need to dump the log from serial console too.
Wayne,
Ok, if guess and check is the only way, I will try that. Most of the files reference each other, so I don’t think I can change one at a time.
Is the UART log from post 5 what you are looking for?
jetsonFlash_uartOutput.txt
Could you let me know what you think of that log, or if I can provide a different log?
I will spend today trying to replace files one at a time, and I will let you know what I find.
Hi,
I just want to clarify this first. How many files did you change on your side in comparison with the the default BSP from jetpack?
As I already told in previous comment, you only need to change kernel dtb, pinmux cfg for most custom board cases.
I don’t see any reason there is “Most of the files reference each other”. I guess you misunderstood something here…
For example, if you don’t know what “kernel dtb” is or what “pinmux cfg” is, please tell. Do not waste too much time if you don’t get this clearly.
Wayne,
I went through and searched my changes in the flasher config files in my project. I traced my error to the file p3668.conf.common in the flasher configs in Linux_for_Tegra folder.
I had changed the file p3668.conf.common to myCarrierBoard.conf.common, since that file referenced the p3509 .dtb files.
Then, in myCarrierBoard.conf.common, I had changed the line from:
PMC_CONFIG=“tegra19x-mb1-padvoltage-p3668-a01.cfg”;
to
PMIC_CONFIG=“myCarrierBoard-padvoltage.cfg”;
This meant there was no PMC_CONFIG file path, and re-defined PMIC_CONFIG. Whoops!
I should have changed it to PMC, but accidentally had PMIC! This caused the MB1 crash, and being stuck at tegrarcm_vt --isapplet on the PC side.
After that fix, I got stuck at a much more helpful error message, that was the result of another error in myCarrierBoard.conf.common.
When I fixed that error, I was able to flash the whole board with my custom .dtb and .cfg for pinmux and padvoltage!
I am curious whether or not I did need to edit the file p3668.conf.common, or leave it alone?
Does the line DTBFILE= define the .dtb flashed by flash.sh -k kernel-dtb?
Since I have it working with my custom .dtb and .cfgs referenced (after fixing my own mistakes!), I think I’ll keep it that way, unless you have any reason not to, for MB1 functionality.
Thanks!
Actually, there is no standard answer for it. If you are pretty sure you won’t any mistake as what you just did. Then whatever file name or file you want to change is ok.
Just make sure all necessary files got flashed.
If you cannot make sure you won’t accidentally change anything, then just use the old one and modify file one by one.
Does the line DTBFILE= define the .dtb flashed by flash.sh -k kernel-dtb?
Yes, that is correct.
Ok, thanks for the confirmation, and I’ll try not to create my own problems in the future.
Do you have a list of files that get flashed, and how they are referenced?
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.