Jump to content

Odroid-C2: diet pi ok, armabian ko


alain

Recommended Posts

HI,

I want use armbian on my odroid-c2.
But I can't start it:
  - Ubuntu xenial 5.40, 3.14.79 loop on 'authentification ... token error'
  - Debian stretch next desktop4.14.30 don't make anything on screen
But DietPi v60.0 Jessie work fine.
The power supply is Odroid model.
I try two sd card, sandisk ultra 64Go and Hc class 10 16Go:
  - dietpi is ok
  - 2 distrib of Armbian are Ko.

About Debian stretch next, the  blue led flash 2 time rapidely, without stop
Could you help me?
Thanks

Edited by alain
Link to comment
Share on other sites

hi,

Thanks for reply. I'll burn the SD cards again to try  armbian. I have try already 2 or 3 times with etcher,  with each sd cards without success .


but i don't understand why DietPi run correctly with same sd cards. No problem occurs

Link to comment
Share on other sites

10 hours ago, alain said:

but i don't understand why


Me neither. Images are tested multiple times and they work. Bash scripts are not really an appropriate reference nor help in diagnostic this problem.

 

Procedure at login is as follows:
root

1234

1234

yournewpass

yournewpass

 

Do this way and you should be fine. 

 

Just to make sure I tested those images once again:
https://dl.armbian.com/odroidc2/Ubuntu_xenial_default_desktop.7z
Boot log: http://ix.io/16qp

https://dl.armbian.com/odroidc2/Ubuntu_xenial_default.7z

Boot log: http://ix.io/16qx

 

Edit: After this fix, upgrading from legacy to mainline also works fine.

Link to comment
Share on other sites

12 minutes ago, alain said:

Hi,
I don't have any doubt about the quality of your great work! really.
I have problem with my board / sd card / power supply, I don't know
I try https://dl.armbian.com/odroidc2/Ubuntu_xenial_default_desktop.7z"
  - ko with 3 differents sdcard
  - ok with emmc -> very good news

I will try with other distrib...


This is low-level problem and most likely related to your SD card.  Odroids are sensitive to them and also brand new UHS type cards can have problems. You will run into the same problem in other distributions.  Waste of time if you don't get to the bottom of the problem.

Instead of distro hopping, invest your time into education:
https://magazine.odroid.com/wp-content/uploads/odroid-c2-user-manual.pdf

 

Quote

Fully compatible microSD cards
• SanDisk microSDHC Memory Card
• SanDisk Ultra microSDHC/microSDXC UHS-I Memory Card
• Samsung SDXC EVO Memory Card
• Toshiba Exceria Memory Card
Partially compatible microSD cards
The following cards may not be able to boot immediately on
ODROID-C2, but instead take about 30 seconds to start the boot up
process. Once the boot processing is done, and the operating system
is running, they perform normally:
• Transcend microSDXC Class 10 UHS-I 300x (Premium)
Chapter 2
25 ODROID C2 USER MANUAL
• Transcend microSDHC Class 10 (Premium)
• Transcend microSDHC Class 6 (Standard)
• Samsung microSD Pro Class 10
• Samsung microSDHC EVO Class 10
• Kingston microSD Class 4
• PNY Turbo Performance Class 10
Class 2/4/6 microSD cards have not been tested with the
ODROID-C2, therefore it is likely that the ODROID-C2 will not boot
properly with them. We strongly recommend to use Class 10/UHS-I
microSD cards, and a SanDisk microSD for full compatibility.

3

 

https://docs.armbian.com/

 

You might find the cause of the problems there.

Link to comment
Share on other sites

i try with 3 differents sdcards:

  - pny sdhc class 10  8go

  - sandisk ultra sdxc class 10 64 go

  - ?name? sdhc class 10 16 go

I have read 'getting started of armbian' and UM of odroid C2.

I have bought power supply, emmc, ...,  directly to harkernel.

but bad luck...

I will work with ubuntu even I prefer debian.

I will waiting for news issue of debian ;-)

thanks for your answeers Igor!

 

 

 

 

Link to comment
Share on other sites

The "scorched Earth" solution might be to disable all HS modes, making your SD card slow as...  Well, an RPi.  The Odroid is also very sensitive to eMMC timing, I'll have to check if the phase timing issue was in 4.14 or not, again, the solution was to significantly limit transfer speeds.  

Link to comment
Share on other sites

https://patchwork.kernel.org/patch/10254657/

 

https://patchwork.kernel.org/patch/10000643/

 

It would seem (and the symptoms agree with the conclusion) this is a board layout problem.  I don't have a board to test this on, however, @Igor I think we should reduce the max frequencies on both the SD and the eMMC, that SD sensitivity has to be a similar issue, the drivers aren't any different for other boards that don't have the problem as far as I know.

Link to comment
Share on other sites

5 minutes ago, TonyMac32 said:

I think we should reduce the max frequencies on both the SD and the eMM


But we already did something to fix issues on eMMC cards on a mainline kernel? I can't reproduce this problem so it's irrelevant if I have the board :)

If this could help and if SD card runs on "Rpi level" I don't mind. Push a patch.

Link to comment
Share on other sites

I could just build a server image for OP to see if that helps, since it seems likely that OP has one of the sensitive boards. If it fixes the issue, then ok, but if not, then I'd rather not handicap the boards needlessly.


@alain which eMMC do you have?




Sent from my Pixel using Tapatalk
 

Edited by TonyMac32
Link to comment
Share on other sites

And that is the one that seems problematic.  Ok, really this should just be as easy as changing the device tree, so I should have a link for a command line image in a few hours (just getting home, food an whatnot)

Link to comment
Share on other sites

@Igor We had reduced the speed to 150 MHz from 200 MHz, but apparently in 4.13 and older kernels, it was actually running at 1/2 the requested speed, so 75 MHz (If I'm reading the thread properly).  I'm matching the upstream at 100 MHz to start.  As for SD I'm just going to drop the clock from 100 MHz to 50 MHz, looking at the vendor kernel they have 85MHz as max, but as noted they still seem sensitive.  Since @alain can't boot properly to install a new dtb package I'm just building a server image to see if it will work.  If it does, hooray and push the bugfix, if it doesn't, well then we have a mystery.

 

So TL;DR:

 

  • eMMC:   down to 100 MHz to match upstream 4.17 WIP
  • SD: down to 50 MHz to try to avoid all the issues.

 

http://electricgraveyard.com/armbian/C2/Armbian_5.42_Odroidc2_Ubuntu_xenial_next_4.14.32.zip

 

Again, I can't test it, but please try it from eMMC and from SD

Link to comment
Share on other sites

In first time I'm tested your new image and no result.  black screens.  but blue led blink...

I have used other screen and surprise,  it works correctly. I don't test with sd card only with emmc.

I have tested with this screen the debian stretch , it works correctly.

so:

with 'old' screen only ubuntu with kernel 3.xx works.

with 'new' screen ubuntu and debian work with kernel 3x and 4x.

I don't have the 'new' screen for long time. but now I know a solution.

THANKS A LOT

Link to comment
Share on other sites

On 6.4.2018 at 12:00 AM, TonyMac32 said:

And that is the one that seems problematic.  Ok, really this should just be as easy as changing the device tree, so I should have a link for a command line image in a few hours (just getting home, food an whatnot)

Just as a remark: I use eight of the 128GB eMMC modules now on eight C2 setups for some days now, without any problems.

I have "ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.14.26-odroidc2" systems with the speed patch included.

 

Before speed patch these eMMCs were a "no go" with Armbian, while smaller ones (16GB usually) worked like a charm.

 

Michael

Link to comment
Share on other sites

Just as a remark: I use eight of the 128GB eMMC modules now on eight C2 setups for some days now, without any problems.
I have "ARMBIAN 5.41 user-built Debian GNU/Linux 9 (stretch) 4.14.26-odroidc2" systems with the speed patch included.
 
Before speed patch these eMMCs were a "no go" with Armbian, while smaller ones (16GB usually) worked like a charm.
 
Michael
Did you apply the patch in your own build then? Just want to compare notes before committing it to the build system.

Sent from my Pixel using Tapatalk

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines