hello
i flashed jetpack5.1.2 into the agx orin module, and did the following two modifications. it works well on the devkit, but there is a big possibility fail booting up on our own carrier board. I want to know how to look into this problem and solve it, thanks
agx-orin.log (9.3 KB)
Hi,
[0000.470] E> BL_CARVEOUT: Failed to allocate memory of size 0x36800000 for CO:44.
[0000.478] C> Task 0x20 failed (err: 0x49490303)
[0000.482] E> Top caller module: BL_CARVEOUT, error module: BL_CARVEOUT, reason: 0x03, aux_info: 0x03
[0000.491] C> Boot Info Table status dump :
01111111001110001111111111111111
That means you are using the wrong memory config.
How did you flash the device?
What do you have in the board config file?
thanks for answering
i modified only Linux_for_Tegra /bootloader/tegra234-mb2-bct-common.dtsi & Linux_for_Tegra /p3701.conf.common following the instruction in the pictures i pasted
first i flashed the orin module on the devkit carrier with command
$ sudo ./flash.sh jetson-agx-orin-devkit mmcblk0p1
then i moved the orin module to our own carrier board, sometimes it can boot up
agx-orin-boot-success.log (99.6 KB)
can you tell me the exact file you mean by board config file, in fact i did’t modify any other files at all
However, you still got this in the successful booting log:
[0000.470] E> BL_CARVEOUT: Failed to allocate memory of size 0x36800000 for CO:44.
[0000.478] C> Task 0x20 failed (err: 0x49490303)
[0000.482] E> Top caller module: BL_CARVEOUT, error module: BL_CARVEOUT, reason: 0x03, aux_info: 0x03
[0000.491] C> Boot Info Table status dump :
01111111001110001111111111111111
Can you please try how it works out if you flash the device with the module being put on your custom carrier board from the beginning?
Your jetson-agx-orin-devkit.conf is kept as the default one?
sorry the usb port on our own carrier board is not working well now, that’s why i chose to flash on the devkit
jetson-agx-orin-devkit.conf is kept default, should i modify it?
I just feel like if it’s really some memory BCT issue, then it should also happen on DevKits because DRAM is directly soldered on the module itself, but not on the carrier board.
Do you know what SKU the module you are using is?
Can you please show me the full flashing log?
Is the custom carrier board different from the DevKit in terms of device tree/pinmux?
If it’s not, then there is no need do do it.
our carrier board do have some differences with the devkit, are there any pages or links talks about how to write our own jetson-agx-orin-devkit.conf
Then you should read this first:
https://docs.nvidia.com/jetson/archives/r35.4.1/DeveloperGuide/text/HR/JetsonModuleAdaptationAndBringUp/JetsonAgxOrinSeries.html
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.