Issues Booting from SD

Post Reply
jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Issues Booting from SD

Unread post by jcst18 » Wed Sep 11, 2019 1:52 pm

Hi, I've been having difficulties using the SD slot on my N2. I was attempting to update Petitboot but the files were never recognized off the SD in both upgrade and recovery mode. I tried to boot Ubuntu off the SD card set to MMC but that doesn't work either (nothing to provide off the UART logs.. blue light doesn't even come on). I'm pretty sure there's a hardware issue, which would be pretty unfortunate. Any help would be appreciated.

User avatar
odroid
Site Admin
Posts: 32360
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 147 times
Been thanked: 325 times
Contact:

Re: Issues Booting from SD

Unread post by odroid » Wed Sep 11, 2019 2:00 pm

Boot Ubuntu from eMMC without SD card.
After booting, plug an SD card and capture "dmesg" output and post it here to find a root cause.

User avatar
tobetter
Posts: 4038
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 43 times
Been thanked: 189 times
Contact:

Re: Issues Booting from SD

Unread post by tobetter » Wed Sep 11, 2019 2:12 pm

If you can get the shell from Petitboot, please do run the command and share the output while your SD card is attached.

# ls -l /dev/mmcblk*

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Wed Sep 11, 2019 2:54 pm

Relevant part from dmesg here..

Code: Select all

[  144.744810] meson-mmc: card IN
[  144.744834] meson-mmc: normal card in
[  144.868846] meson-mmc: actual_clock :400000, HHI_nand: 0x80
[  144.868852] meson-mmc: [meson_mmc_clk_set_rate_v3] after clock: 0x1000023c
[  145.063344] meson-mmc: actual_clock :0, HHI_nand: 0x80
[  145.063349] meson-mmc: [meson_mmc_clk_set_rate_v3] after clock: 0x1000023c
[  145.080789] meson-mmc: actual_clock :400000, HHI_nand: 0x80
[  145.080794] meson-mmc: [meson_mmc_clk_set_rate_v3] after clock: 0x1000023c
[  145.094615] meson-aml-mmc ffe05000.sd: divider requested rate 200000000 != actual rate 199999997: ret=0
[  145.094622] meson-mmc: actual_clock :199999997, HHI_nand: 0x80
[  145.094624] meson-mmc: [meson_mmc_clk_set_rate_v3] after clock: 0x10000245
[  145.094627] meson-mmc: Data 1 aligned delay is 0
[  145.094630] meson-mmc: sd: clk 199999997 tuning start
[  145.096160] meson-mmc: sd: rx_tuning_result[0] = 40
[  145.096200] meson-mmc: Tuning transfer error: nmatch=0 tuning_err:0xffffffac
[  145.099554] meson-mmc: sd: rx_tuning_result[2] = 40
[  145.101223] meson-mmc: sd: rx_tuning_result[3] = 40
[  145.102757] meson-mmc: sd: rx_tuning_result[4] = 40
[  145.102760] meson-mmc: sd: best_win_start =2, best_win_size =4
[  145.102763] meson-mmc: sd: sd_emmc_regs->gclock=0x10000245,sd_emmc_regs->gadjust=0x42000
[  145.102776] sd: new ultra high speed SDR104 SDXC card at address 0001
[  145.102778] sd: clock 199999997, 4-bit-bus-width
                
[  145.109117] mmcblk1: sd:0001 GC2QT 59.6 GiB 
[  145.110857]  mmcblk1: p1
[  145.764800] meson-mmc: card OUT
[  145.764823] meson-mmc: card out
[  145.765880] sd: card 0001 removed
Output from shell is..
/dev/mmcblk0
/dev/mmcblk0boot0
/dev/mmcblk0boot1
/dev/mmcblk0p1
/dev/mmcblk0p2
/dev/mmcblk0p3
/dev/mmcblk0p4
/dev/mmcblk0rpmb

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Wed Sep 11, 2019 3:10 pm

Update: I formatted the card and flashed Ubuntu minimal again.. those errors disappeared from output but it still can't boot off of SD.

Weirdly Petitboot is now finally recognizing both OS on the eMMC.. absolutely no idea how that happened or how it was related to the SD because it never worked before.

EDIT: Nope.. gone from Petitboot again. Not even sure how to recreate what happened. Also, new log once I've booted into Ubuntu:

Code: Select all

[   30.104553@0] meson-mmc: card IN                               
[   30.308549@0] meson-mmc: card OUT                                            
[   30.544939@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.545736@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.552330@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.559864@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.565235@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.573076@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.577888@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.585566@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.590542@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.596790@5] meson-mmc: Command retried failed line:634, cmd:8              
[   30.603703@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.609089@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.615684@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.623201@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.628588@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.636246@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.641242@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.648527@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.653895@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.660496@5] meson-mmc: Command retried failed line:634, cmd:55             
[   30.667479@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.672875@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.679472@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.686989@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.692376@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.700003@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.705374@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.712973@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.718373@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.724972@5] meson-mmc: Command retried failed line:634, cmd:55             
[   30.725115@0] meson-mmc: card IN                                             
[   30.735156@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.740563@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.747158@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.754667@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.760060@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.767672@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.773060@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.780843@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.786061@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.792656@5] meson-mmc: Command retried failed line:634, cmd:55             
[   30.799645@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.805041@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.811635@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.819150@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.824542@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.832268@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.837542@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.844822@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.850193@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.856789@5] meson-mmc: Command retried failed line:634, cmd:55             
[   30.862797@0] sd: error -110 whilst initialising SD card                     
[   30.869153@0] meson-mmc: sd: resp_timeout,vstat:0x9dff0800,virqc:3fff        
[   30.874460@0] meson-mmc: sd: err: wait for desc write back, bus_fsm:0x7      
[   30.881057@5] meson-mmc: meson_mmc_irq_thread_v3() 616: set 1st retry!       
[   30.888569@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.893962@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.901288@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.906615@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.913897@0] meson-mmc: sd: resp_timeout,vstat:0xa1ff2800,virqc:3fff        
[   30.919270@0] meson-mmc: sd: err: wait for irq service, bus_fsm:0x8          
[   30.925517@5] meson-mmc: Command retried failed line:634, cmd:1              
[   31.140563@0] meson-mmc: card OUT

User avatar
tobetter
Posts: 4038
Joined: Mon Feb 25, 2013 10:55 am
languages_spoken: Korean, English
ODROIDs: X, X2, U2, U3, XU3, C1
Location: Paju, South Korea
Has thanked: 43 times
Been thanked: 189 times
Contact:

Re: Issues Booting from SD

Unread post by tobetter » Wed Sep 11, 2019 3:36 pm

jcst18 wrote:
Wed Sep 11, 2019 3:10 pm
Update: I formatted the card and flashed Ubuntu minimal again.. those errors disappeared from output but it still can't boot off of SD.

Weirdly Petitboot is now finally recognizing both OS on the eMMC.. absolutely no idea how that happened or how it was related to the SD because it never worked before.

EDIT: Nope.. gone from Petitboot again. Not even sure how to recreate what happened. Also, new log once I've booted into Ubuntu:
I am not sure if it's a hardware issue or not, what I am seeing from the logs is that your uSD is recognized but detached after many errors. What's the vendor or model of you uSD? It probably works on PC flawlessly, right?
These users thanked the author tobetter for the post:
jcst18 (Wed Sep 18, 2019 5:10 am)

User avatar
odroid
Site Admin
Posts: 32360
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 147 times
Been thanked: 325 times
Contact:

Re: Issues Booting from SD

Unread post by odroid » Wed Sep 11, 2019 3:39 pm

The SD card slot/interface look okay at least. So it seems not to be a hardware issue probably.

Did you change the boot mode slide-switch and remove the eMMC?
Do you have any other SD card for testing?
Could you see any UART message something like this?

Code: Select all

G12B:BL:6e7c85:7898ac;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:0;SD:0;READ:0;CHK:1F;USB:8;

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Wed Sep 11, 2019 4:01 pm

This is actually the second micro SD card I'm using. The first one had problems as well but it turned out to be a knockoff. This one is a Samsung EVO Select, just purchased and works perfectly on my PC.
I did change the boot switch and the UART displays:

Code: Select all

G12B:BL:6e7c85:7898ac;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:200;

User avatar
odroid
Site Admin
Posts: 32360
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 147 times
Been thanked: 325 times
Contact:

Re: Issues Booting from SD

Unread post by odroid » Wed Sep 11, 2019 4:40 pm

The card seems to be detected but SoC couldn't read boot blobs probably.

Did you flash ubuntu-18.04.3-4.9-minimal-odroid-n2-20190806.img.xz image with Etcher?

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Thu Sep 12, 2019 2:38 am

odroid wrote:
Wed Sep 11, 2019 4:40 pm
The card seems to be detected but SoC couldn't read boot blobs probably.

Did you flash ubuntu-18.04.3-4.9-minimal-odroid-n2-20190806.img.xz image with Etcher?
Yeah, that's what I used.

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Tue Sep 17, 2019 8:43 am

Any ideas on what I can do here?

User avatar
odroid
Site Admin
Posts: 32360
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 147 times
Been thanked: 325 times
Contact:

Re: Issues Booting from SD

Unread post by odroid » Tue Sep 17, 2019 11:04 am

Sorry for my late response.

<1> If there is a bootable SDcard in the slot, I could see this message.

Code: Select all

G12B:BL:6e7c85:7898ac;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:0;SD:0;READ:0;0.
bl2_stage_init 0x01
<2> If don't plug a card, I met this one.

Code: Select all

SD?:20000;
<3> If I plug a non-bootable SD card, I can see this one.

Code: Select all

SD?:0;SD:0;READ:0;CHK:1F;USB:8;
Can you compare the messages once again?

Your previous message seemed that the SoC couldn't detect the card insertion due to uncertain hardware problem.
In that case, please contact "odroid at hardkernel dot com" with a link of this post.
They will help your RMA process if you purchased the board from our web-store directly.
Otherwise, contact your local distributor/reseller.
These users thanked the author odroid for the post:
jcst18 (Wed Sep 18, 2019 5:09 am)

jcst18
Posts: 11
Joined: Mon Aug 26, 2019 11:25 am
languages_spoken: english
ODROIDs: N2
Has thanked: 2 times
Been thanked: 0
Contact:

Re: Issues Booting from SD

Unread post by jcst18 » Wed Sep 18, 2019 5:09 am

Well, uh.. it seems like all three cases provide the exact same output as before:

Code: Select all

G12B:BL:6e7c85:7898ac;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:200;
I guess I'll contact Odroid for RMA.

Thanks for trying to help (tobetter included), I appreciate your patience considering how difficult tech support is over a forum. Hopefully I can get the new unit up and running soon enough.

Post Reply

Return to “Issues”

Who is online

Users browsing this forum: No registered users and 3 guests