• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Orange pi pc plus Armbian unable to boot from emmc
1 1

40 posts in this topic

Recommended Posts

Hi guys

 

I am having some issues with booting from emmc

 

created a  sdcard with th latest armbian version for the orange pi pc plus

can boot it without problems

 

updated and upgraded everything.

then ran nand-sata-install all seems to be going ok but after that it wont boot from emmc without sd card inserted

 

I am pretty sure I am missing something obvious  lol

 

any help with be greatly appreciated

 

 

 

 

 

 

Share this post


Link to post
Share on other sites

humz ok that did not work for me

but it seems there is also a new kernel and the file located in

 

usr/lib/linux-u-boot-orangepipcplus_5.23_armhf  is 5.23 instead of 5.20

 

dd if=/usr/lib/linux-u-boot-orangepipcplus_5.23_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk2 bs=1024 seek=8

the copy was succesfull but still no boot from emmc

maybe eter to do it before anything is updated ;)

Share this post


Link to post
Share on other sites

tried to format emmc storage manual no problems there

 

these are the steps I am doing now

 

writing new image to card latest armbian 5.20 that's on the oramge pi site

 

booting from card all ok no issues seen.

 

doing no updates at all going straight into  root terminal and typing nand-sata-install

Share this post


Link to post
Share on other sites

dd if=/usr/lib/linux-u-boot-orangepipcplus_5.23_armhf/u-boot-sunxi-with-spl.bin of=/dev/mmcblk2 bs=1024 seek=8

 

Since you're using legacy image this is not supposed to work at all (eMMC being mmcblk2 is something that happens with mainline kernel but not legacy). Please get a serial console since we have a few rather strange reports regarding eMMC on the Plus: https://github.com/igorpecovnik/lib/pull/540

 

No progress being made so far (since if we ask for logs and don't get logs then...)

Share this post


Link to post
Share on other sites

what image should I use then ?  I can do a serial debug if you want but will it show any emmc errors ?

Ok, we get 'it does not work!' reports, we can not reproduce the issue since it doesn't happen on our devices and we don't get logs from users even if we ask them. How to proceed?

 

Why don't you provide just a boot log from serial console for any of the 'it does not work!' cases? I've not the slightest idea how this log will look like and that's the reason we need those logs! If I would know the contents I wouldn't need it.

Share this post


Link to post
Share on other sites

the log file with sd card inserted

 

U-Boot SPL 2016.09-armbian (Sep 15 2016 - 07:38:36)
DRAM: 1024 MiB
Trying to boot from MMC1

U-Boot 2016.09-armbian (Sep 15 2016 - 07:38:36 +0200) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: Xunlong Orange Pi PC Plus
I2C:   ready
DRAM:  1 GiB
MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   phy interface0
eth0: ethernet@1c30000
Hit any key to stop autoboot:  2 1 0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2789 bytes read in 157 ms (16.6 KiB/s)
## Executing script at 43100000
gpio: pin PL10 (gpio 298) value is 1
gpio: pin PG11 (gpio 203) value is 1
59 bytes read in 118 ms (0 Bytes/s)
** File not found /boot/.next **
** Unrecognized filesystem type **
** File not found .next **
37596 bytes read in 436 ms (84 KiB/s)
3114592 bytes read in 321 ms (9.3 MiB/s)
5025168 bytes read in 468 ms (10.2 MiB/s)
## Loading init Ramdisk from Legacy Image at 43300000 ...
   Image Name:   uInitrd
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    3114528 Bytes = 3 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Using machid 0x1029 from environment

Starting kernel ...

[sun8i_fixup]: From boot, get meminfo:

 Start: 0x40000000

 Size: 1024MB

ion_carveout reserve: 160m@0 256m@0 130m@1 200m@1

ion_reserve_select: ion chipid  [0x2004620!

ion_reserve_common: ion reserve: [0x50000000, 0x60000000]!

Share this post


Link to post
Share on other sites

anybody the problem is that for some reason the script is unable to copy data correctly to the emmc

can anybody  point out to me how to repartition the emmc and point to the correct rootfs and bootfs

 

after that the script should run fine

Share this post


Link to post
Share on other sites

is there a new image for that or just run the new script ?

 

in my case it seems there is something going wrong with setting the partitions

because  if I flash the server version instead of destop it works fine

but it changes the size of the bootfs partition

Share this post


Link to post
Share on other sites

almost

 

Last login: Wed Nov 23 18:44:19 2016 from 192.168.1.1
root@orangepipc:~# sudo ln -fs /boot/bin/orangepipcplus.bin  /boot/script.bin
ln: failed to create symbolic link ' /boot/script.bin': No such file or directory
root@orangepipc:~#
 

 

ok just copied the file manualy as a work around that seem to have done the trick

script now runs nope hopefully it will complete without errors

 

btw this image seems to work a lot beter then the old one

but still have random disconnects on wifi and lan when connected with putty

realy anying when you are running the script and it gets disconnected

Share this post


Link to post
Share on other sites

Beta images still have some troubles, that's why they are beta :P  ... try with disabling power management:

iwconfig wlan0 power off

Wifi should be more responsive after that.

Share this post


Link to post
Share on other sites

Awesome thanks Igor

you are the man

 

did find a other issues that's not related to the image but was probably causing most of my problems

the beefy 2.5 amp 5 volt adaptor I was using was not realy up to the job because voltage was dropping to 4.5 volt  under load.

so that probably Caused the disconnects and network hickups and random lockups

Share this post


Link to post
Share on other sites

the beefy 2.5 amp 5 volt adaptor I was using was not realy up to the job because voltage was dropping to 4.5 volt  under load.

so that probably Caused the disconnects and network hickups and random lockups

As always. And with OPi Zero it will get even worse since the Micro USB port there will encourage users to use the crappiest phone 'Chargers' somewhere lying around just to blame Armbian for their PSU troubles. :(

Share this post


Link to post
Share on other sites
Until the next reboot. That's why h3consumption exists. 

 

Sure.

 

I would propose that we switch those defaults to off since power management is causing serious troubles on some wireless chips. Sometimes it's necessary to disable it to be functional at first place. Some people would think that wifi doesn't work at all because it needs seconds to respond, when PM is enabled ...

 

Who needs / want's to save some power he will presumably seek for such how-to and found this way. What do you think?

Share this post


Link to post
Share on other sites

As always. And with OPi Zero it will get even worse since the Micro USB port there will encourage users to use the crappiest phone 'Chargers' somewhere lying around just to blame Armbian for their PSU troubles. :(

yep and the funny thing is that I already knew this to start off with

so they say assumption is the mother of all fuckups I would say measure before you start don't assume any power adaptor rated for 2 amps is capable of doing so  lol

Share this post


Link to post
Share on other sites

ok all works great now everthing is stable 

nand-sata-install script runs fine

but still no boot from emmc

 

boot.cmd seems fine

but fstab file doet not have any location In it

dos anybody have an example of that file

 

 

UUID=ed0bb37c-e98d-47fd-96d7-25ffc9ef3a7a / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
/var/swap none swap sw 0 0

 

root@orangepipc:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:32   0    4M  1 disk
mmcblk1boot1 179:48   0    4M  1 disk
mmcblk0      179:0    0 14.9G  0 disk
└─mmcblk0p1  179:1    0 14.8G  0 part /
mmcblk1      179:16   0  7.3G  0 disk
└─mmcblk1p1  179:17   0  7.2G  0 part

 

 

boot.cmd file

 

# default values
setenv load_addr "0x44000000"
setenv rootdev "/dev/mmcblk1p1"
setenv verbosity "1"
setenv console "both"
setenv disp_mem_reserves "off"
setenv disp_mode "1920x1080p60"
setenv rootfstype "ext4"

# Print boot source
itest.b *0x28 == 0x00 && echo "Booting from SD"
itest.b *0x28 == 0x02 && echo "Booting from eMMC or secondary SD"

if load mmc 0 ${load_addr} /boot/armbianEnv.txt || load mmc 0 ${load_addr} armb$


 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

1 1

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.