Hey, sorry for the late answer, we are on holiday.
Unfortunately, I don’t remember which value I wrote.
Can you please guide whether I can download the current EEPROM values, or if there are default values to recover to?
hello ophirg123,
you can dump the eeprom by $ sudo i2cdump -f -y 2 0x50. if this board is bootable,
otherwise, you’ll need to program the same values to pass the flash process.
The board is not bootable.
Which values do I need to program and how?
You have maybe an example?
I got the logs from the flash process that I tried to do:
logs.txt (9.3 KB)
By the way now when I try to reflash, I get the message:
ophir@ophir-VirtualBox:~/nvidia/nvidia_sdk/JetPack_4.6_Linux_JETSON_NANO_TARGETS/Linux_for_Tegra$ sudo BOARDID=3448 FAB=0000 ./flash.sh jetson-nano-devkit mmcblk0p1
###############################################################################
L4T BSP Information:
R32 , REVISION: 6.1
###############################################################################
Target Board Information:
Name: jetson-nano-devkit, Board Family: t210ref, SoC: Unknown,
OpMode: production, Boot Authentication: ,
Disk encryption: disabled ,
###############################################################################
Error: The Actual SoC ID(0x42) mismatches intended jetson-nano-devkit SoC ID(0x21).
hello ophirg123,
it’s my assumption you’ve program the chip-id as 0x42, which should be 0x21.
please assign the tegraid with -x options, i.e. $ sudo BOARDID=3448 FAB=0000 ./flash.sh -x 0x42 jetson-nano-devkit mmcblk0p1
you should also modify the flash.sh to make it recognize this board.
for example,
case ${hwchipid} in
0x21) socname="Tegra 210"; mach_dir="t210ref"; ;;
+ 0x42) socname="Tegra 210"; mach_dir="t210ref"; ;;
0x18) socname="Tegra 186"; mach_dir="t186ref"; ;;
0x19) socname="Tegra 194"; mach_dir="t186ref"; ;;
please have a try, thanks!
Hey Jerry,
I think we are making a little progress every time.
This is the error right now:
logs (1).txt (4.9 KB)
please refer to this post. The xml file is also needed for providing the board info.
Your parameters maybe different from this case because they are emmc module but yours is sdcard module.
I followed the link you attached and it seemed to start flashing the board, but it got stuck:
[ 168.0447 ] Writing partition APP with system.img
[ 7007.5419 ] … ] 017%
Error: Return value 3
Command tegradevflash --pt flash.xml.bin --storageinfo storage_info.bin --create
Failed flashing t210ref.
The logs:
2021_20_09_logs.txt (13.1 KB)
-
Can you provide what you’ve added to the config file? Did you ever change the content inside xml file?
-
Is your host a Virtual box?
Hey,
I modified the next files as they said on the other topic:
p3448-0000.conf.common -
+BCFFILE=“bootloader/${target_board}/cfg/board_config_p3448.xml”
p3449-0000+p3448-0000-qspi-sd.conf -
+BOARDID=“3448”;
+FAB=“000”
About your other question, YES I am using Virtualbox because I don’t have a pure Linux PC.
I read now that it is probably because of the VM.
They said that I need to set the USB to ECHI.
I will try that now.
Edit:
Now it got stuck at the line -
[ 0.3184 ] tegrarcm --chip 0x21 0 --rcm rcm_list_signed.xml --skipuid
I will try to do the whole setup at Linux PC. If you have other idea why it got stuck at that line, I will try it.
I succeeded to flash board on a regular Linux PC.
The logs:
27_09_21_logs.txt (13.3 KB)
What is the next step? I tried to connect it to a monitor with HDMI but I get no signal at all.
Use the uart console to see if you can dump the log.
The next step is use the uart console to access the board and then modify the module eeprom crc value.
After that, this board should work fine in both flash and boot up. I mean you no longer needs to add extra xml file to make flash work.
Hey, I tried to connect to the UART console debug session with two different USB to TTL adapters but nothing seems to work. I get no chars at the console.
I am not sure what is the problem but I think maybe I should use the RMA.
Do you have other jetson nano to validate if your usb-ttl setup here is correct?
Yeah, I checked it on my Jetson Nano 2GB and it worked like the Jetson Hacks video. I got into the terminal.
But when I connect the broken Jetson Nano devkit, I get nothing.
Ok, sounds like time for RMA.
Thank you very much for the help!
I am sure that a lot of people will benefit from the whole process that we did until now.