I have tested , as next command,
mkdir hanwha
tar xpf ./Jetson_linux_r36.3.0_aarch64.tbz2 -C hanwha/
when i use next command:
the problem is
this problem is occurred sometimes (but only happened first time installation)
first time, when i build,
yeseterday compile error is occurred
please attach full error log.
When running apply_binaries.sh, system will chroot and use apt command to install package.
i uploaded it.
sometimes error !.. i think when i first build only, it happend (in Korea)
after compile is done, this problem is never occurred.
./bootloader/tegraparser_v2 file
If communication is OK, Compile is OK
But if compiling is done at least once, compiling is everytime OK.
please attach your full log as text file. Such screenshot has poor quality when checking.
now it is not reproduced now in my server … sorry about it.
when i do command “./apply_binaries.sh”
`25/2/20 PM04:00 yesterday i execute “./apply_binaries.sh”
the result is compile err.
`25/2/21 PM04:00
./bootloader/tegraparser_v2
This won’t communicate with NVIDIA server. Only apply_binaries.sh would use apt-get to install files.
Please just report issue if you could find out a method that can 100% reproduce it.
Please install the Secureboot package to use initrd flash for fused board
*
Step 1: Generate flash packages *
*
Create folder to store images to flash
###############################################################################
###############################################################################
[ 0.0476 ] tegrasign_v3.py --key None --getmode mode.txt
*** no-flash flag enabled. Exiting now… ***
User can run above saved command in factory environment without
Example:
$ cd bootloader
$ sudo bash ./flashcmd.txt
and then My company use tegraparser_v2 (for Arm64)
vhw@hw-Recoder:/mnt/sdb/songholee_upgrade_for_teslar$ tree -L 4
├── ai_box.conf (for HVC HW )
└── bootloader
├── LICENSE.tegraopenssl
├── Orin-ai_box_bsp-gpio-default.dtsi (for HVC HW )
├── Orin-ai_box_bsp-padvoltage-default.dtsi (for HVC HW )
├── Orin-ai_box_bsp-pinmux.dtsi (for HVC HW )
├── tegrabct_v2 (for Arm64)
├── tegradevflash_v2 (for Arm64)
├── tegrahost_v2 (for Arm64)
├── tegraopenssl (for Arm64)
├── tegraparser_v2 (for Arm64)
├── tegrarcm_v2 (for Arm64)
└── tegrasign_v2 (for Arm64)
and then
but i used always
strong text
Hi @songho.lee
There are some points to clarify here
Could you “attach” your log as a file but not just copy and paste? Your comment is hard to read because the format totally messed up.
Is this a custom board made by yourself or it is from 3rdparty vendor?
Why not just do a full flash first? It sounds like you just keep using no-flash command.
What does that mean “for Arm64”? All of the tool provided by sdkmanager is for amd64 to run…
Sorry to say that but your English comment is hard to read too. Maybe you could just put your comment in Korean and I can translate that by myself.
here are some points to clarify here
Could you “attach” your log as a file but not just copy and paste? Your comment is hard to read because the format totally messed up.v36.4.3_logs.txt (13.4 KB)
Is this a custom board made by yourself or it is from 3rdparty vendor?
이문제는 보드에서 일어나는게 아니고, 컴파일하는 서버에서 발생한다.
한국에 내서버는 잘 발생하지 않고,
미국의 고객의 서버에서는 항상 발생한다.
Why not just do a full flash first? It sounds like you just keep using no-flash command.
we download from cv5 board(our camera board) to nvidia orin nx using usb port
우리회사는 CV5보드를 사용하여 Nvidia orin nx chip에 usb 포트를 통하여 다운로드 한다.
What does that mean “for Arm64”? All of the tool provided by sdkmanager is for amd64 to run…
Arm64 files is received by nvidia.
Arm64파일은 nvidia에서 받았다
Sorry to say that but your English comment is hard to read too. Maybe you could just put your comment in Korean and I can translate that by myself.
Hi,
Could you try to use amd64 version and see if you can still reproduce this issue?
Actually this tool is not public so we may not discuss it here.
Dear Nvidia
i exatly want to know below error meanings
Return value 4 : ??
=============================================
$ cd bootloader
$ sudo bash ./flashcmd.txt
question3) What does “signed/flash.idx is not found” mean?
Hi,
It is actually not needed to explain. Based on previous experience, even knowing the meaning of “return value 4” won’t help your issue.
Also, your problem is just in the beginning of this error.
[ 0.0506 ] Invalid partition type pva_fw
The rest of part are just the result from it. You don’t need to dig into why flash.idx is not there. Previous error already led to that result.
Please discuss your problem in the offline mail. It is not something that should be discussed in this forum.
system
March 26, 2025, 6:39am
19
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
