Hi All,
Could you please help me to Flash Jetson AGX Xavier 32GB [p2888-0004] version correctly?
I have followed the answer posted on a community to flash the Jetson Xavier correctly but when we check the board information and memory partitions it seems to be related to the model Jetson Xavier 16Gb one. ( p2888-0001 ]
I have used the following command the flash the module
sdkmanager --cli install --logintype devzone --staylogin true --product Jetson --host --target P2888-0004 --targetos Linux --version 4.4.1 --flash all --license accept
internally it uses the following command
./flash.sh jetson-agx-xavier-devkit mmcblk0p1
I have explicitly provided the target version to as follow
./flash.sh -C -B p2888-0004 jetson-agx-xavier-devkit mmcblk0p1
But still, it took the p2888-0001 version by looking into logs
The ubuntu shows the following information
The total size should be 32Gb rather than 16 GB
Free -h shows proper 32 GB
Hi
This issue sounds weird.
Do you mean the tools like “free” or “top” all tell you the memory there is 32 but that jetson tool (sorry, I don’t know what the name is) tells you it is 16G device? Please note that tool is not released by NV so I am not sure how it detects the board version.
Could you share me the uart log and dmesg from your device during boot up?
Hi Wayne,
Thank you very much for your swift response. Please find attached the log for your reference.
Quick summary
cat /etc/os-release
NAME=“Ubuntu”
VERSION=“18.04.5 LTS (Bionic Beaver)”
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME=“Ubuntu 18.04.5 LTS”
VERSION_ID=“18.04”
HOME_URL=“https://www.ubuntu.com/”
SUPPORT_URL=“https://help.ubuntu.com/”
BUG_REPORT_URL=“https://bugs.launchpad.net/ubuntu/”
PRIVACY_POLICY_URL=“Data privacy | Ubuntu”
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
cat /proc/version
Linux version 4.9.201-tegra (buildbrain@mobile-u64-5285-d7000) (gcc version 7.3.1 20180425 [linaro-7.3-2018.05 revision d29120a424ecfbc167ef90065c0eeb7f91977701] (Linaro GCC 7.3-2018.05) ) #1 SMP PREEMPT Fri Feb 19 08:42:04 PST 2021
cat /usr/local/cuda/version.txt | sed ‘s/\CUDA Version //g’
10.2.89
sudo cat /proc/device-tree/compatible
nvidia,galennvidia,jetson-xaviernvidia,p2822-0000+p2888-0001nvidia,tegra194
cat /sys/module/tegra_fuse/parameters/tegra_chip_id
25
Based on log BOARD ID as follow
Board ID(2888) version(400) sku(0004) revision(L.0)
LOG FileJetson-Xavier.log (64.1 KB)
Please let me know if you need any further information.
Hello,
I need the boot up log from uart. Do you have that?
Hi Wayne,
Could you let me know where the uart log located ? I would check and if available will share with you.
Regards,
Ashish
Plug the micro usb cable to the micro usb port, connect it to your ubuntu host.
Use tools like minicom to open /dev/ttyUSB3 with baudrate 115200. The log will spew during boot up process.
https://elinux.org/Jetson/General_debug
Also want to ask @rbonghi… where does jetson_release get the board info?
Could you kindly share?
Hi Wayne,
Please find attached uart log. uart.log (28.0 KB)
Regards,
Ashish
From the log, I can tell you that your hardware is a 32GB module…
The ramcode is 0x2 which indicates the hardware is definitely the 32GB device.
Maybe only the jetson_stats gives the wrong info here. I am still waiting for @rbonghi’s input here.
Please note that jetson_stats is not an official tool…
Hi Wayne,
I have checked the Github repo where @rbonghi contributed the script which identified the board information
I have used the same script and output as follow
NVIDIA Jetson AGX Xavier [16GB]
L4T 32.5.1 [ JetPack UNKNOWN ]
Ubuntu 18.04.5 LTS
Kernel Version: 4.9.201-tegra
CUDA 10.2.89
CUDA Architecture: 7.2
OpenCV version: 4.1.1
OpenCV Cuda: NO
CUDNN: 8.0.0.180
TensorRT: 7.1.3.0
Vision Works: 1.6.0.501
VPI: ii libnvvpi1 1.0.15 arm64 NVIDIA Vision Programming Interface library
The L4T 32.5.1 [ JetPack UNKNOWN ] is UNKNOWN because the script checks for up to 4.4 jetpacks.
Regards,
Ashish
Hi @WayneWWW
Could you able to provide any further assistance?
Regards
Ashish
Sorry that I don’t know what kind of assistance you want here…?
You said p2888-0004 is the 32GB device, that is correct. And please check how/what does that script parse and you shall know what happens…