Purchased Jetbot V3 kit for Christmas and cannot get Nvidia nano to boot out of the box. Tried reflashing image several times and different sd cards. Tried with nothing else connected to it besides power and hdmi and all I get is a green light on the carrier board. Tried re-seating the nano also. Anything else to try?
Try hooking the HDMI up to a monitor and booting this image https://sfecdn.s3.amazonaws.com/jetbot/ … _linux.zip - see how far it gets into the installation and report back https://learn.sparkfun.com/tutorials/as … rom-nvidia
Tried your suggested image and still no boot. Like before, I get green power led then after a second or two monitor says “no signal”. I believe this is the same image I’ve been trying all along. I am able to read the App (ext4) partition on the sd card so I know card is fine.
What’s next?
Do you have the option of hooking up serial console? https://www.youtube.com/watch?v=Kwpxhw41W50
You can also try flashing an earlier image of JetPack (non-jetbot image, 4.3 and 4.5 are good options) and see if that gets it booting (then try swapping back to a Jetbot image)
I was able to connect to console. This is what I get on boot:
[21:09:19:599] [0000.125] [L4T TegraBoot] (version 00.00.2018.01-l4t-e82258de)␍␊
[21:09:19:646] [0000.130] Processing in cold boot mode Bootloader 2␍␊
[21:09:19:646] [0000.135] A02 Bootrom Patch rev = 1023␍␊
[21:09:19:646] [0000.138] Power-up reason: pmc por␍␊
[21:09:19:646] [0000.141] No Battery Present␍␊
[21:09:19:646] [0000.144] pmic max77620 reset reason␍␊
[21:09:19:646] [0000.147] pmic max77620 NVERC : 0x40␍␊
[21:09:19:646] [0000.151] RamCode = 0␍␊
[21:09:19:646] [0000.153] Platform has DDR4 type RAM␍␊
[21:09:19:646] [0000.156] max77620 disabling SD1 Remote Sense␍␊
[21:09:19:646] [0000.161] Setting DDR voltage to 1125mv␍␊
[21:09:19:646] [0000.165] Serial Number of Pmic Max77663: 0x140679␍␊
[21:09:19:646] [0000.172] Entering ramdump check␍␊
[21:09:19:646] [0000.175] Get RamDumpCarveOut = 0x0␍␊
[21:09:19:691] [0000.179] RamDumpCarveOut=0x0, RamDumperFlag=0xe59ff3f8␍␊
[21:09:19:691] [0000.184] Last reboot was clean, booting normally!␍␊
[21:09:19:691] [0000.188] Sdram initialization is successful ␍␊
[21:09:19:691] [0000.192] SecureOs Carveout Base=0x00000000ff800000 Size=0x00800000␍␊
[21:09:19:691] [0000.199] Lp0 Carveout Base=0x00000000ff780000 Size=0x00001000␍␊
[21:09:19:691] [0000.204] BpmpFw Carveout Base=0x00000000ff700000 Size=0x00080000␍␊
[21:09:19:691] [0000.210] GSC1 Carveout Base=0x00000000ff600000 Size=0x00100000␍␊
[21:09:19:691] [0000.216] GSC2 Carveout Base=0x00000000ff500000 Size=0x00100000␍␊
[21:09:19:722] [0000.222] GSC4 Carveout Base=0x00000000ff400000 Size=0x00100000␍␊
[21:09:19:722] [0000.228] GSC5 Carveout Base=0x00000000ff300000 Size=0x00100000␍␊
[21:09:19:722] [0000.234] GSC3 Carveout Base=0x000000017f300000 Size=0x00d00000␍␊
[21:09:19:722] [0000.250] RamDump Carveout Base=0x00000000ff280000 Size=0x00080000␍␊
[21:09:19:771] [0000.256] Platform-DebugCarveout: 0␍␊
[21:09:19:771] [0000.259] Nck Carveout Base=0x00000000ff080000 Size=0x00200000␍␊
[21:09:19:771] [0000.265] Non secure mode, and RB not enabled.␍␊
[21:09:19:771] [0000.269] BoardID = 3448, SKU = 0x0␍␊
[21:09:19:771] [0000.272] QSPI-ONLY: SkipQspiOnlyFlag = 0␍␊
[21:09:19:771] [0000.276] Nano-SD: checking PT table on QSPI …␍␊
[21:09:19:771] [0000.281] Read PT from (2:0)␍␊
[21:09:19:771] [0000.296] Using BFS PT to query partitions ␍␊
[21:09:19:794] [0000.302] Loading Tboot-CPU binary␍␊
[21:09:19:809] [0000.330] Verifying TBC in OdmNonSecureSBK mode␍␊
[21:09:19:860] [0000.340] Bootloader load address is 0xa0000000, entry address is 0xa0000258␍␊
[21:09:19:860] [0000.347] Bootloader downloaded successfully.␍␊
[21:09:19:860] [0000.351] Downloaded Tboot-CPU binary to 0xa0000258␍␊
[21:09:19:860] [0000.356] MAX77620_GPIO5 configured␍␊
[21:09:19:860] [0000.359] CPU power rail is up␍␊
[21:09:19:860] [0000.362] CPU clock enabled␍␊
[21:09:19:860] [0000.366] Performing RAM repair␍␊
[21:09:19:860] [0000.369] Updating A64 Warmreset Address to 0xa00002e9␍␊
[21:09:19:860] [0000.374] BoardID = 3448, SKU = 0x0␍␊
[21:09:19:860] [0000.377] QSPI-ONLY: SkipQspiOnlyFlag = 0␍␊
[21:09:19:860] [0000.381] Nano-SD: checking PT table on QSPI …␍␊
[21:09:19:875] [0000.385] Loading NvTbootBootloaderDTB␍␊
[21:09:19:950] [0000.452] Verifying NvTbootBootloaderDTB in OdmNonSecureSBK mode␍␊
[21:09:20:034] [0000.523] Bootloader DTB Load Address: 0x83000000␍␊
[21:09:20:034] [0000.528] BoardID = 3448, SKU = 0x0␍␊
[21:09:20:034] [0000.531] QSPI-ONLY: SkipQspiOnlyFlag = 0␍␊
[21:09:20:034] [0000.535] Nano-SD: checking PT table on QSPI …␍␊
[21:09:20:034] [0000.540] Loading NvTbootKernelDTB␍␊
[21:09:20:107] [0000.606] Verifying NvTbootKernelDTB in OdmNonSecureSBK mode␍␊
[21:09:20:194] [0000.679] Kernel DTB Load Address: 0x83100000␍␊
[21:09:20:194] [0000.683] BoardID = 3448, SKU = 0x0␍␊
[21:09:20:194] [0000.686] QSPI-ONLY: SkipQspiOnlyFlag = 0␍␊
[21:09:20:194] [0000.690] Nano-SD: checking PT table on QSPI …␍␊
[21:09:20:194] [0000.696] Loading cboot binary␍␊
[21:09:20:306] [0000.812] Verifying EBT in OdmNonSecureSBK mode␍␊
[21:09:20:383] [0000.854] Bootloader is corrupted!␍␊
[21:09:20:383] [0000.857] Error in NvTbootLoadBinary: 0x14 !␍␊
[21:09:20:383] [0000.861] BoardID = 3448, SKU = 0x0␍␊
[21:09:20:383] [0000.864] QSPI-ONLY: SkipQspiOnlyFlag = 0␍␊
[21:09:20:383] [0000.868] Nano-SD: checking PT table on QSPI …␍␊
[21:09:20:383] [0000.873] PT: Partition RBL NOT found ! ␍␊
[21:09:20:383] [0000.876] Warning: Find Partition via PT Failed␍␊
[21:09:20:383] [0000.881] Error is 1 ␍␊
Tried Jetpack 4.5.1 and got same results as above.
OK, I have gotten an update from our team:
"Basically, users need to upload a blank/default image with the jetpack 4.5 to upload the latest firmware on the board before the new image will work (see here: https://jetbot.org/master/software_setup/sd_card.html)
Users should flash a card and boot with this image (update the firmware):
https://drive.google.com/file/d/1o08RPD … sp=sharing
Then they should be able to use this image (that might have been shipped out with the latest boards):
https://sfecdn.s3.amazonaws.com/jetbot/ … _linux.zip
If that isn’t the user’s issue, the read out looked like a corrupted bootloader was the problem and we’d have to point them to Nvidia for more troubleshooting (I don’t think we have any boards left to replace right now). I believe, I remember seeing some instructions on a forum for fixing the bootloader, but it required a linux computer to run the SDK Manager (https://developer.nvidia.com/drive/sdk-manager)"
Apologies for the troubles getting going, this is a new issue that first appeared last week :-/
We’ll get ya squared away
A corrupt boot loader was the issue. I got it working by using sdkmanager. Here is what I did.
Software Setup
I loaded Ubuntu 18.04.6 on an old laptop
Downloaded and Installed latest sdkmanager for Jetson Nano
Jetson Hardware Setup
Inserted sdcard
Inserted jumper to use barrel connector for power
Inserted jumper for FC Rec (forced recovery mode)
Connected micro usb to laptop.
Connected usb mouse/kbd
Connected hdmi
Procedure (simplified)
Started sdkmanager on laptop
Powered Jetson and removed FC Rec jumper
When Sdkmanager recognized Jetson Nano, I selected Jetson Nano Developer kit.
I Followed sdkmanager instructions to install jetpack 4.5.1. (This took a long while)
Once complete, I removed power, and removed power jumper.
Removed usb from laptop and plugged it into the Jetbot battery to boot Jetson.
After Jetson booted, I shutdown using mouse.
Removed power (unplugged battery)
Reflashed sdcard with provided SF Jetbot image
Booted again and now oled showed “no connection “
Using mouse and keyboard I connected Jetson to my WiFi.
Oled now displayed IP address.
Now the fun begins.
I know this was an uncommon occurrence and disappointing to say the least, but I thank you for all the help in finally getting to the bottom of this. I learned a lot, and hopefully my experience will help others too.
Thanks for the final update! Should be very useful if someone runs into a similar issue
Glad to hear it got worked out in the end
Sparkun Forum:
]
I am sorry to bother you.
I am learning in hopes of teaching summer school using the Sparkfun Jet Bot
So far all (4) jetbots are having the same issue the error
I used this version as the pre-loaded image did not work for AI Kit v3.0
This is one I re-imaged SP sparkfun_4GB_jetbot_v01-21
** SparkFun JetBot AI Kit v3.0 Powered by Jetson Nano
Almost works these are the errors:
error 1: nvdc: nvdcEventThread select failed: Bad file descriptor
jetbot@jetson-4-3:~$
error 2 Running the motor test from Jyputer NB:
from jetbot import Robot
Error loading module ublox_gps: No module named ‘serial’
Very sorry, the module has been updated and tested to work. Either try again with another w-gps or pip install sparkfun-ublox-gps --upgrade.
If you have version 1.1.3, then you are in the right place.
Tried to update the pip no luck : guidance and instructions
Also;
This did not resolve the issue: I appreciate the suggestion though:
Start here https://learn.sparkfun.com/tutorials/as … rom-nvidia and grab the image for your kit, noting that there are 2 different versions (scroll down a bit, v 1.10 and 1.1, select the one that matches your particular SD card)
After you’ve gone through all of those steps (last one on that page is installing the qwiic package) you should be able to use the examples that follow on the next page
Russell Turner
SparkFun Tech Support
SparkFun Electronics, Inc.
6333 Dry Creek Parkway
Niwot, CO. 80503
Thanks for your time
jeff
Any update on my post?
Thanks
I would uninstall that Python package. It requires the use of a serial port, which sounds like it is disabled on your board. This should remove the error you are seeing.
sudo pip uninstall sparkfun-ublox-gps