I flashed the developer kit recently on an nv3 ssd. Everything works perfectly but it keeps rebooting by itself over and over again for no reason. The supplier sent a 19V, 2.37A,45W power supply with the kit.
Is this a software problem, or a power problem?
Only way to discover that will be to connect to the debug port and see what is going on and where it hangs.
Hi,
Yes as foxsquirrel1 suggest
Please refer to this to dump the UART log for us to review
Thanks
Thanks @foxsquirrel1 and @DavidDDD for the reply.
Here’s my UART log for your reference.
bootUART.txt (126.8 KB)
It smells like a power problem, I see the ubuntu login so it might be a power issue or it would not have gotten to the login. If you have a lab supply try running from it and watch the current and see what happens.
Can you boot from SD with out any problems? Remove your nvme and boot from SD image and see what happens. At this point all you can do is try different stuff. I did notice not anything serious, the imx219 error from csi camera, guess on that, might not be an issue.
I got a new power supply rated 19V, 3.42A, 65W. The frequency of restart got much less, but it still happens. So I;m still not sure if it was the rote of the problem or something else. Can you help? Is it possible that i got a faulty developer kit from nvidia and should ask for replacement?
Hi abdulhady,
What is your jetpack version?
Please execute below command and share the results
cat /etc/nv_tegra_release
Thanks
My Jetpack version:
Source: nvidia-jetpack (6.1)
Version: 6.1+b123
the output of the command:
R36 (release), REVISION: 4.0, GCID: 37537400, BOARD: generic, EABI: aarch64, DATE: Fri Sep 13 04:36:44 UTC 2024
KERNEL_VARIANT: oot
TARGET_USERSPACE_LIB_DIR=nvidia
TARGET_USERSPACE_LIB_DIR_PATH=usr/lib/aarch64-linux-gnu/nvidia
Just to clarify … I don’t see anything indicate a reboot in previous log. What I saw is just a one time boot up log.
If this is a log that happened after your so-called “reboot”, then you should share the log before that reboot happened… but not only giving me such log.
It is about the context here. Logs before and after the reboot happened both matters.
Hi,
You could append -C ${filename} to dump the log directly
For example:
sudo minicom -C ${filename} -D /dev/${USBNAME} -8 -b 115200
Thanks
Ok thanks, I’ll connect the UART and keept i logging until it reboots and send you the logs
UART_log.txt (966.1 KB)
Here you will find multiple reboot operations that happened automatically. I hope this could be helpful
I saw some logs from ethernet related driver that is causing the watchdog and then reboot.
Just a one more test. Could you flash your board with sdkmanager + rel-35.6 (jetpack5) and see if you still see this issue?
Thanks for the reply. For some reason i can’t choose older jetpack versions, they are grayed out and unclickable. I’m able to choose only 6.1 and 6.0. any ideas?
The grey text already told you the reason.
I have no space on my device to setup a lower linux version. Is there anything else we can do? are you sure it’s related to the jetpack version i’m using
No, actually I feel it is more like hardware problem.
Just an experiment to try. If you cannot try, please RMA this device.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.