Customer Boot Error Troubleshooting Advice
Customer encountered booting error after duplicating SD card due to variable mismatch in disk_read function. Advice on resolving the issue provided based on the specific environment and procedures followed. Multiple attempts made using different SD cards and methods without success. Suggestions to address variable differences in the code to resolve the error.
Uploaded on Mar 10, 2025 | 0 Views
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
1. Issue : Customer could not confirm booting up(u-boot) after duplicating SD card. They got following error message on console. ---- Error reading cluster ** Unable to read file u-boot.img ** SPL: failed to boot from all boot devices ### ERROR ### Please RESET the board ### ---- Customer confirmed reason why this message occur as shown below. - ret variable and nr_blocks variable did not match in function of disk_read() of ~fs/fat/fat.c (When they confirm value of those, ret=0 and nr_blocks=8.) 2. Question : Could you please give your advice which point will affect this error(cause difference ret and nr_blocks 3. Environment : - Customer create their program based on Linux processor SDK ver 08_06_00_42 - They confirmed this issue under their custom board (They have two custom board, and they confirmed same condition for both board.) Please see next slide about how they duplicate SD.
4. Additional information : 4-1. Procedure to duplicate SD card (Case 1 (Use dd command)): 4-1-1. They prepare following three SD card. SD1 : RMSDE-016GU1A (buffalo INC (16GB)) SD2 : Same as SD1 one SD3 : SDSQUAR-032G-JN3MA (SanDisk INC (32GB)) 4-1-2. They write default tisdk-default-image-am62xx-evm.wic.xz by using balenaEtcher tool to SD1 . After that, they replace their custom binary files from original files on boot partition. 4-1-3. They confirmed booting up correctly on their custom board with SD1 . 4-1-4. They generate img file by using following dd command. And write it to SD2 . Command : $ sudo dd if=/dev/sdb of=./sdcard1.img bs=4096 count=165120; sync $ sudo dd if=./sdcard1.img of=/dev/sdb bs=4096; sync 4-1-5. They could NOT confirm booting up correctly on their custom board with SD2 . 4-1-6. They used SD3 instead of SD2 , however they also could NOT confirm booting up correctly on their custom board wich SD3 .
4. Additional information : 4-2. Procedure to duplicate SD card (Case 2 (use Clone Drive on BalenaEtcher tool )): 4-2-1. They prepare following four SD card. From SD1 SD4 : Same parts number with 16GB. 4-2-2. They performed format by using following tool for SD1-SD4 . https://www.sdcard.org/ja/downloads-2/formatter-2/ 4-2-3. They write default tisdk-default-image-am62xx-evm.wic.xz by using balenaEtcher tool to SD1 . After that, they confirmed booting up correctly on TI AM62 EVM . 4-2-4. They duplicate filesystem by using Clone Drive from SD1 to SD2-SD4 . After that, they confirmed booting up correctly on TI AM62 EVM . 4-2-5. They replace their custom binary files for SD1 . After that, they confirmed booting up correctly on their custom board . 4-2-6. They duplicate filesystem by using Clone Drive from SD1 to SD2-SD4 . After that, they could NOT confirm booting up correctly on their custom board with SD2-SD4 .
Information for E2E (2024/1/8 9:28 posted) >Try leaving out the `count=` parameter. When copying an SD card you'd always want to cope the _entire_ device. We have already performed following command as well. Command : $ sudo dd bs=1M if='/dev/sdb' of='./sdcard1.img' status=progress $ sudo dd bs=1M if='./sdcard1.img' of='/dev/sdb' status=progress Block size is 1M and removed count parameter. However, we also have same error. And also performed format before performing dd command.
Confirmation result for request from E2E (2024/1/13) Can they do a verify of the data read from the SD card, and after it's written to a new SD card? They can do something like this... Here is procedure which customer confirmed. 1. Customer performed SD format for 2 SD card(We call SD1 and SD2 ) by using SD Card Formatter tool. 2. Customer write tisdk-default-image-am62xx-evm.wic to SD2 by using balenaEtcher tool. 3. Customer replace binary file (u-boot) for SD2 . 4. Customer get hash value by using sha256sum command. ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb cb33b2a0aa4f8c644760c159e1014da27320e54be68a371cf9014a64afc73c19 /dev/sdb 5. Customer copy this filesystem to PC by using dd command. ubuntu@ubuntu-VirtualBox:~/0112$ sudo dd if=/dev/sdb of=sdcard.img status=progress; sync; 15483257344 bytes (15 GB, 14 GiB) copied, 3314 s, 4.7 MB/s 30244864+0 records in 30244864+0 records out 15485370368 bytes (15 GB, 14 GiB) copied, 3314.89 s, 4.7 MB/s
Confirmation result for request from E2E (2024/1/13) (Cont) 6. Customer get hash value from generated img file. ubuntu@ubuntu-VirtualBox:~/0112$ sha256sum ./sdcard.img cb33b2a0aa4f8c644760c159e1014da27320e54be68a371cf9014a64afc73c19 ./sdcard.img 7. Customer write copied files system to SD1 card. ubuntu@ubuntu-VirtualBox:~/0112$ sudo dd if=sdcard.img of=/dev/sdb status=progress; sync; 15485157888 bytes (15 GB, 14 GiB) copied, 48157 s, 322 kB/s 30244864+0 records in 30244864+0 records out 15485370368 bytes (15 GB, 14 GiB) copied, 48157.7 s, 322 kB/s 8. Customer get hash value from SD1 card. ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb 6fa10abe72e616d738f8e6ca8e60dc98e0c0b2cd35706ccadfc3946c93381acc /dev/sdb ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb; e264fdce349c7760d04d7f4a2f287f81b1527399bf8fc678163bdc74f6e02540 /dev/sdb ubuntu@ubuntu-VirtualBox:~/0112$ time sudo sha256sum /dev/sdb; 6ced17ec57f061992307c7f4659870f40e5bb5ca21ff061de2437b77dd6c1776 /dev/sdb
Confirmation result for request from E2E (2024/1/13) (Cont) Conclusion 1 : * When they check hash value on SD2 (original SD card), they got same hash value between copied file system and SD2 file system as shown below. Hash value from original SD card(SD2) : ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb cb33b2a0aa4f8c644760c159e1014da27320e54be68a371cf9014a64afc73c19 /dev/sdb Hash value from copied (PC) : ubuntu@ubuntu-VirtualBox:~/0112$ sha256sum ./sdcard.img cb33b2a0aa4f8c644760c159e1014da27320e54be68a371cf9014a64afc73c19 ./sdcard.img
Confirmation result for request from E2E (2024/1/13) (Cont) Conclusion 2 : * When they check hash value on SD1 (copied SD card), they got different hash value between original file system and SD1 file system as shown below. Hash value from copied (PC) (same value as original SD card( SD2) : ubuntu@ubuntu-VirtualBox:~/0112$ sha256sum ./sdcard.img cb33b2a0aa4f8c644760c159e1014da27320e54be68a371cf9014a64afc73c19 ./sdcard.img Hash value from SD1 (copied SD card) : ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb 6fa10abe72e616d738f8e6ca8e60dc98e0c0b2cd35706ccadfc3946c93381acc /dev/sdb
Confirmation result for request from E2E (2024/1/13) (Cont) Conclusion 3 : * Hash value from SD1 is difference every time customer perform sha256 command. ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb 6fa10abe72e616d738f8e6ca8e60dc98e0c0b2cd35706ccadfc3946c93381acc /dev/sdb ubuntu@ubuntu-VirtualBox:~/0112$ sudo sha256sum /dev/sdb; e264fdce349c7760d04d7f4a2f287f81b1527399bf8fc678163bdc74f6e02540 /dev/sdb ubuntu@ubuntu-VirtualBox:~/0112$ time sudo sha256sum /dev/sdb; 6ced17ec57f061992307c7f4659870f40e5bb5ca21ff061de2437b77dd6c1776 /dev/sdb
