Problem with SD Boot


#1

Hello folks,

Prelude:
I have been playing with the board for the past few days and today I’m kind of stuck.
I was able to flash (with SD card) Android as well as Linux (few times) on my board but today I can’t boot on my SD card anymore.

Before someone asked I always follow the tuto of https://github.com/96boards/documentation/wiki/Dragonboard-410c-Installation-Guide-for-Linux-and-Android.
I never tried to flash with another method than the SD card before that issue.
I also haven’t install anything custom (build/kernel), I just used the ressources provided by 96board.
I tried with several SD card and they working fine.

SD boot:
The last distrib that I used is Android and when I tried to reflash Linux with the SD Card install it just keep skipping the NOOBS launcher and keep starting on the last distribution. (I also tried then to flash with android and recover image but same results).

USB boot:
I gave a try with the Dragonboard Update Tool (using USB) and I succesfully flashed windows IOT…but now I’m stuck with windows IOT.

Fastboot :
I then tried to use the fastboot method but because I’m not able to install it with the SD card (chapter create install a rescue image) I found a menu when powering the board and pressing (s2 (pwr) and s3(+) => 16-fastboot app). Not sure that it is enough to use the fastboot method but my board was recognize on my host with the command fastboot devices. But as soon as I tried to flash it through the fastboot flash command it says that partition on the target does not exist.

Is there any other way to flash the board with the debian distrib through USB?
It really looks like I corrupted my board no chance to recover it in any way ?

I’m really open to any suggestion you can have.

Thanks by advance,

Jérôme.


#2

Hi @jtis

I am also not sure what happened to your image.

Would this help? Have you tried this?

cat /dev/zero > /dev/disk/by-partlabel/boot


#3

Hello atsuka,

Thanks for you answer.
So I finaly plug my UART to check what is going on during the boot and try the command to erase the boot but here is the boot I got :


Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00274
S - IMAGE_VARIANT_STRING=HAAAANAZA
S - OEM_IMAGE_VERSION_STRING=HARV-DKULLANG
S - Boot Config, 0x000002e1
S - Core 0 Frequency, 0 MHz
B -      1545 - PBL, Start
B -      3490 - bootable_media_detect_entry, Start
B -    113492 - bootable_media_detect_success, Start
B -    113497 - elf_loader_entry, Start
B -    115614 - auth_hash_seg_entry, Start
B -    115824 - auth_hash_seg_exit, Start
B -    131079 - elf_segs_hash_verify_entry, Start
B -    190923 - PBL, End
B -    159088 - SBL1, Start
B -    210267 - pm_device_init, Start
D -     14304 - pm_device_init, Delta
B -    224968 - boot_flash_init, Start
D -        30 - boot_f }„Ё}Ñ„€!B -    281088 - Info: using default cdt
D -     47610 - boot_config_data_table_init, Delta - (0 Bytes)
B -    283863 - CDT version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B -    290848 - sbl1_ddr_set_params, Start
B -    294538 - cpr_init, Start
D -         0 - cpr_init, Delta
B -    300150 - Pre_DDR_clock_init, Start
D -       183 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -    312747 - pm_driver_init, Start
D -      6893 - pm_driver_init, Delta
B -    328302 - clock_init, Start
D -        30 - clock_init, Delta
B -0 
     J€HH    FÉÑ5
D -        61 - SEC Image Load}!€°1”x	=  @ j  š¸°2 UQQe  œ€P,F ø     #236 
 b¼€1 R   ytdb
 ᕍÕÑ¥½¹± Delta
B -    440023 - SBL1, End
D -    283284 - SBL1, Delta
S - Flash Throughput, 74000 KB/s  (1763400 Bytes,  23546 us)
S - DDR Frequency, 400 MHz
 

UEFI Start : 535 mS
PROD Mode  : Off
CONF File  : uefiplatWP.cfg
FW Version : uefi_pw.win.3.1.1531038.2078.M8916RELTTNWZA2078
Build Info : 32b Sep 15 2015 20:33:04
 SEC End    : 838 mS
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
HOBLIST address in DXE = 0xBFDDE010
FV Hob            0x80200000 - 0x8031FFFF
FV Hob            0x8384A000 - 0x83BE9FFF
FV2 Hob           0x8384A000 - 0x83BE9FFF
  - 0xBFFA8000  EnvDxe.efi
  - 0xBFFA2000  RuntimeDxe.efi
  - 0xBFF81000  InterruptDxe.efi
  - 0xBFF75000  ArmCpuDxe.efi
ConvertPages: Incompatible memory types
  - 0xBFF65000  SecurityDxe.efi
  - 0xBFF60000  SmemDxe.efi
  - 0xBFF4F000  DALSys.efi
  - 0xBFF4A000  HWIODxeDriver.efi
  - 0xBFF44000  ChipInfo.efi

Then I’m reaching the EBL command. I am able to switch to a shell but it seems that the command
" cat /dev/zero > /dev/disk/by-partlabel/boot " return Error. Unable to redirect file. I guess this is because I’m currently using a windows IOT system…

Is there any flash serial tool that I could use to recover my flash ?

Thanks,

Jérôme.


#4

hello,

so you are saying that you can no longer boot from SD? Have you tried reflashing a new SD card? I assume you’ve already checked that the switch button was in SD boot mode…

There is no USB tool to flash the Linux image. In fact I didn’t know there was a USB tool for Windows… maybe we could use this tool to flash eMMC… do you have a link to this tool or instructions? How do you use it?

Maybe you can try this too: https://github.com/96boards/documentation/wiki/Dragonboard-410c-Installation-Guide-for-Linux-and-Android#create--install-a-rescue-image. It’s another SD card image that is supposed to bring you into fastboot mode. I would like to see the UART traces when you boot with this SD image.


#5

Hi,

I have tried 3 differents SD card (2* class 10 and 1* class 4) with the debian-SD-install.img and the android as well. I also test on an other Dragonboard and the boot with the same SD card started as expected.
Yes I always checked twice when I was doing my tests that the switch was correctly set on SD boot.

You can find the windows tool here in “Software - Windows”: https://developer.qualcomm.com/hardware/dragonboard-410c/tools
Instructions : https://ms-iot.github.io/content/en-US/win10/DB410c.htm
You might encounter the following error (but also fix in the tuto) : https://github.com/ms-iot/content/issues/752

I will run the traces with the SD-Rescue.img this evening and post it here.

Jérôme.


#6

hi jerome,

can you please also try this image:

http://people.linaro.org/~georgi.djakov/db410c_sd.img

This is not meant to be a fix… but more debug… this is an SD card with a linux kernel and rootfs on the SD card. We have seen one similar problem as you report a few days ago, and we couldn’t boot the SD rescue, nor the SD install… but we could boot this one… it’s probably worth investigating more what’s going on…

thanks for your help.

note: just dd the .img on an SD, as usual.


#7

Hello,

So I did the different tests and unfortunatly it did not work as we would expect :
Here are the logs with the sd_rescue_img :


Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00274
S - IMAGE_VARIANT_STRING=HAAAANAZA
S - OEM_IMAGE_VERSION_STRING=HARV-DKULLANG
S - Boot Config, 0x000002e3
S - Core 0 Frequency, 0 MHz
B -      1545 - PBL, Start
B -      3490 - bootable_media_detect_entry, Start
B -   1229016 - bootable_media_detect_success, Start
B -   1229021 - elf_loader_entry, Start
B -   1230673 - auth_hash_seg_entry, Start
B -   1230883 - auth_hash_seg_exit, Start
B -   1246381 - elf_segs_hash_verify_entry, Start
B -   1306223 - PBL, End
B -   1328153 - SBL1, Start
B -   1392691 - pm_device_init, Start
D -     14762 - pm_device_init, Delta
B -   1407971 - boot_flash_init, Start
D -         0 - boot_f   =¸˜ ™}B -   2471018 - Info: using default cdt
D -   1054537 - boot_config_data_table_init, Delta - (0 Bytes)
B -   2473794 - CDT version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B -   2480748 - sbl1_ddr_set_params, Start
B -   2484438 - cpr_init, Start
D -         0 - cpr_init, Delta
B -   2490081 - Pre_DDR_clock_init, Start
D -       213 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -   2502677 - pm_driver_init, Start
D -      9516 - pm_driver_init, Delta
B -   2520855 - clock_init, Start
D -        30 - clock_init, Delta
B -D (     02 €HnA@ S WHˆ-        61 - SEC Image Loade € <code></code>   " @@@@´€‘  €:h  @  
@ (   2 •ÕÑ¥½¹± Delta
B -   2632394 - SBL1, End
D -   1306620 - SBL1, Delta
S - Flash Throughput, 74000 KB/s  (1763400 Bytes,  23546 us)
S - DDR Frequency, 400 MHz
 

UEFI Start : 2660 mS
PROD Mode  : Off
CONF File  : uefiplatWP.cfg
FW Version : uefi_pw.win.3.1.1531038.2078.M8916RELTTNWZA2078
Build Info : 32b Sep 15 2015 20:33:04
 SEC End    : 2964 mS
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
HOBLIST address in DXE = 0xBFDDE010
FV Hob            0x80200000 - 0x8031FFFF
FV Hob            0x8384A000 - 0x83BE9FFF
FV2 Hob           0x8384A000 - 0x83BE9FFF
  - 0xBFFA8000  EnvDxe.efi
  - 0xBFFA2000  RuntimeDxe.efi
  - 0xBFF81000  InterruptDxe.efi
  - 0xBFF75000  ArmCpuDxe.efi
ConvertPages: Incompatible memory types
  - 0xBFF65000  SecurityDxe.efi
  - 0xBFF60000  SmemDxe.efi
  - 0xBFF4F000  DALSys.efi
  - 0xBFF4A000  HWIODxeDriver.efi
  - 0xBFF44000  ChipInfo.efi

I then have few lines with unreadable characters

The following logs are for the SD_custom_img that NDEC sent :


Format: Log Type - Time(microsec) - Message - Optional Info
Log Type: B - Since Boot(Power On Reset),  D - Delta,  S - Statistic
S - QC_IMAGE_VERSION_STRING=BOOT.BF.3.0-00274
S - IMAGE_VARIANT_STRING=HAAAANAZA
S - OEM_IMAGE_VERSION_STRING=HARV-DKULLANG
S - Boot Config, 0x000002e3
S - Core 0 Frequency, 0 MHz
B -      1545 - PBL, Start
B -      3490 - bootable_media_detect_entry, Start
B -   1228971 - bootable_media_detect_success, Start
B -   1228976 - elf_loader_entry, Start
B -   1231110 - auth_hash_seg_entry, Start
B -   1231320 - auth_hash_seg_exit, Start
B -   1246564 - elf_segs_hash_verify_entry, Start
B -   1306406 - PBL, End
B -   1035566 - SBL1, Start
B -   1085708 - pm_device_init, Start
D -     14274 - pm_device_init, Delta
B -   1100379 - boot_flash_init, Start
D -        30 - boot_f.ë9¤Ð   B -   2163182 - Info: using default cdt
D -   1054293 - boot_config_data_table_init, Delta - (0 Bytes)
B -   2165927 - CDT version:3,Platform ID:24,Major ID:1,Minor ID:0,Subtype:0
B -   2172911 - sbl1_ddr_set_params, Start
B -   2176602 - cpr_init, Start
D -         0 - cpr_init, Delta
B -   2182214 - Pre_DDR_clock_init, Start
D -       183 - Pre_DDR_clock_init, Delta
D -         0 - sbl1_ddr_set_params, Delta
B -   2194810 - pm_driver_init, Start
D -      6862 - pm_driver_init, Delta
B -   2210365 - clock_init, Start
D -        61 - clock_init, Delta
B -Ln@D Rp<code></code> Oad<code></code> …ÉÑ5
D -        61 - SEC Image LoadeC1 t<code></code> %”€ %”€Ln ‚:h €A%  Á‘5
D 
º€ ‚J
ŠMExecution, Delta
B -   2322819 - SBL1, End
D -   1289632 - SBL1, Delta
S - Flash Throughput, 74000 KB/s  (1763400 Bytes,  23515 us)
S - DDR Frequency, 400 MHz
 

UEFI Start : 2658 mS
PROD Mode  : Off
CONF File  : uefiplatWP.cfg
FW Version : uefi_pw.win.3.1.1531038.2078.M8916RELTTNWZA2078
Build Info : 32b Sep 15 2015 20:33:04
 SEC End    : 2962 mS
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
Loading DxeCore at 0x008382B000 EntryPoint=0x0083843F54
HOBLIST address in DXE = 0xBFDDE010
FV Hob            0x80200000 - 0x8031FFFF
FV Hob            0x8384A000 - 0x83BE9FFF
FV2 Hob           0x8384A000 - 0x83BE9FFF
  - 0xBFFA8000  EnvDxe.efi
  - 0xBFFA2000  RuntimeDxe.efi
  - 0xBFF81000  InterruptDxe.efi
  - 0xBFF75000  ArmCpuDxe.efi
ConvertPages: Incompatible memory types
  - 0xBFF65000  SecurityDxe.efi
  - 0xBFF60000  SmemDxe.efi
  - 0xBFF4F000  DALSys.efi
  - 0xBFF4A000  HWIODxeDriver.efi
  - 0xBFF44000  ChipInfo.efi

I got few lines unreadable but more than with the SD_rescue

As you can see it did not change anything for me.

I usually flash it with win32diskimager but I also tried with the dd method through a VM.

Don’t you think that we can manage to use the windows tool to flash our sd image through usb as it is flashing raw data?

Jérôme.


#8

it might be possible to use the USB flasher… but that means we need to understand the format of the image they use…

I might need to work (soon) on the opposite , e.g. add support for W10 in the SD installer… in which case I will probably get more information about the image format… so hopefully with that, i will be able to use the USB flasher for Linux images as well …

I am escalating your specific issue with qcom, as I am running out of ideas at the moment…


#9

hi,

since you have Windows running on the board… let’s try to make use of it :wink:

can you check if SD card is working from Windows? This is to rule out any physical connection issue with the SD…

I don’t know how to check or do that, since I have not used Windows… but I was told it is supposed to work at least.


#10

Hello,

Well I need someone to try the windows version to check twice but the list tree of the devices is not updating whether my SD card is plugged in or not.

In the device tree I can only see the SD host controller (SD card plugged in or not) :
-Qualcomm SoC Secure Digital host controller
-SD Storage Class Controller
-Disk drive

Jérôme.


#11

Hi All,
I am with similar but little different problem.

I had installed Windows 10 IOT core on my db410c. Now my Mouse is not working.
I can not do anything.
I tried installing linux from a SD card. But I am not able to select anything during NOOBS .

Also one more observation, some times I see a little movement in Mouse. it took 30-40 mins for me to bring my mouse over install icon on NOOBS screen. But click events are not being accepted.

Even though I see my keyboard LEDs blinking during boot up, keyboard selection on NOOBS screen does not work… not even Esc.
Unfortunately I dont have a serial cable to debug. I think normal FTDI232 based 3.3V or 5V serial cables wont work with DB410C…
Any help ?
Thanks in advance.


#12

Hi All , I think I have the same issue as described at the post
http://www.96boards.org/forums/topic/dragonboard-keyboardmouse-and-micro-usb-not-responding/
Thanks


#13

HI All ,

Even I am stuck exactly like not able to flash any OS using SD card.
Is there any way to come out of this problem.
Note : I was trying to load the android into my DB_410C board which was running with Debian before.

Please Note : I dont have UART cables in order to collect the serial logs.


#14

Hi @shan2911

Please describe which instructions you are following, what problems you observe and what is happening on the LEDs when you try to boot the installer.


#15

Hi ,
I followed the steps as mentioned in the below steps.

Regarding the Observations :
1.After trying to boot with the sd card [0-1-0-0] "SD Boot Switch ON " , I am getting the below message
“Wired Netwrok access is required to use NOOBS without local images”
2.After clicking close -> Its prompting a message saying all emmc will be overwritten .
3.After clicking “yes” , with in Fraction of seconds its displaying a message “Flashing has completed and OS installed successfully”
4.After I clicked OK and try to reboot by changing switch positions to [0-0-0-0]

Regarding LED blinks :
1.During flashing process “User LEDS” [1-0-0-0] blinks with green color.
2.Once I remove the sd card and try to boot No LEDS [0-0-0-0] are blinking.

It will be great help if somebody rescue from this problem.

Please let me know if you need any other details.

Thanks


#16

Odd. I don’t think we create an SD recovery image without a local image. What image did you download?


#17

HI ,
I downloaded the image from the below location


To be specific in that Snapshot 99


#18

HI ,

I am able to boot the board to Fastboot mode using SD Rescue image (dragonboard410c_sdcard_rescue-88.zip)
I have downloaded the image from the below path
https://releases.linaro.org/96boards/dragonboard410c/linaro/rescue/latest/

I flashed the image to uSD card and booted the board(Pin Config : 0100) to fastboot mode .
when I tried to flash the images to the eMMC , facing below issue.
fastboot flash partition gpt_both0.bin : PASS
fastboot flash hyp hyp.mbn
sending ‘hyp’ (56 KB)…
OKAY [ 0.006s]
writing ‘hyp’…
FAILED (remote: partition table doesn’t exist)
finished. total time: 0.013s
Same error I am getting for the other partitions flashing also.

Any pointers will be very helpful