Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Can't boot Armbian-Stretch image on hummingboard2 edge v1.5 Som

Featured Replies

So I downloaded Armbian Stretch image here https://www.armbian.com/hummingboard-2/

and dd it onto an SD Card. As it didn't produce any output during boot after 'uncompressing kernel' I had to add 'console=both' into the armbianEnv.txt. After that I could see that I land into (initramfs). It looked like it couldn't see the rootfs for some reason. So additionally I've changed rootdev to 'rootdev=/dev/mmcblk0p1' in the armbianEnv.txt. Still the same problem

Quote

No init found. Try passing init= bootarg.

(initramfs) mmc0: error -110 whilst initialising SD card

mmc0: error -110 whilst initialising SD card

 

here is the full boot log https://pastebin.com/K64xKHBd

 

What am I doing wrong?

 

2. Provided that the problem above is easy to fix, how do I start a script after the first boot? Solidrun images have /etc/runonce.d/ scripts but nothing like that in Armbian rootfs. I've seen a template in the /boot but is it possible to start a script to allocate a new partition after the first boot?

 

The only reason why I want to try Armbian is because I cannot use Solidrun image to boot from eMMC with the v1.5 SOC. And I've seen some patches merged into Armbian to solve this problem

8 minutes ago, torba said:

The only reason why I want to try Armbian is because I cannot use Solidrun image to boot from eMMC with the v1.5 SOC. And I've seen some patches merged into Armbian to solve this problem


They were merged into (testing) DEV branch, U-boot 2018.03 ... You can find images on the bottom of the download page. I have to note that I can't test this since we don't have a board with eMMC.

  • Author

right, but I can't boot neither from emmc nor from an SD Card

  • Author

ah you mean a complete image. I thought it just a u-boot. Ok, I'll test

  • Author

so, i have tested the dev image. With the armbian_dev image been flashed on an sd card I can boot into it. But there's no /dev/mmcblk2 device visible which is the emmc. So I boot into solidrun image flashed the armbian_dev image onto /dev/mmcblk2 and rebooted. Here's the output:

Quote

U-Boot SPL 2018.03-armbian (May 30 2018 - 19:24:03 +0000)
Trying to boot from MMC1
Card did not respond to voltage select!
spl: mmc init failed with error: -95
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

 

it is still looks for an sd card.

  • Author

last commit 4 months ago. Doesn't look very active development to me. Well thanks anyway

3 minutes ago, torba said:

last commit 4 months ago. Doesn't look very active development to me. Well thanks anyway


Well, that's active enough :) I have seen some bits regarding eMMC in the commit logs ... while we use mainline u-boot sources, where some parts might be missing. Perhaps it's only a configuration issue. Support for eMMC is hard to implement without eMMC boards and time for R&D.

Guest
This topic is now closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.