4 4
Tido

Le Potato - writing armbian to eMMC

Recommended Posts

I followed balbes instructions and successfully copied the system from my USB drive to the eMMC. Removed the drive and rebooted and all started well and the system was up.

I then edited fstab to add a line for automounting a usb HD (which worked well when running on the flash drive). I also did modeprobe wifi_dummy and found the names of the modules which I added to the modules file.

Now when I rebooted the system, it went into emergency mode. Here are some questions for those who have tried this:

Here are some important questions:

1- is it not possible to edit fstab once the system is running from FLASH?

2- How to automatically run the modprobe wifi_dummy command so that the wifi works on bootup?

3- is it possible to run apt-get update && apt-get upgrade && apt-get dist-upgrade while running from NAND?

4- can the swap partition be moved to the external USB disk drive?

5- is there an easy way to let the system install all new software (like lamp) on the USB drive

 

Thanks again! At least i am still alive.. hardly breathing though

Share this post


Link to post
Share on other sites
16 hours ago, Eddy_T said:

I followed balbes instructions and successfully copied the system from my USB drive to the eMMC. Removed the drive and rebooted and all started well and the system was up.

I then edited fstab to add a line for automounting a usb HD (which worked well when running on the flash drive). I also did modeprobe wifi_dummy and found the names of the modules which I added to the modules file.

Now when I rebooted the system, it went into emergency mode. Here are some questions for those who have tried this:

Here are some important questions:

1- is it not possible to edit fstab once the system is running from FLASH?

2- How to automatically run the modprobe wifi_dummy command so that the wifi works on bootup?

3- is it possible to run apt-get update && apt-get upgrade && apt-get dist-upgrade while running from NAND?

4- can the swap partition be moved to the external USB disk drive?

5- is there an easy way to let the system install all new software (like lamp) on the USB drive

 

Thanks again! At least i am still alive.. hardly breathing though

Don't create doubles in different themes.

Share this post


Link to post
Share on other sites

Hi @balbes150, I have installed some Add-ons to Kodi and I wanted to make use of the remote-control RC6 (Gateway). Reading in the main thread I found that due to dtb the remote will not work on my image. I have this running on eMMC: Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_mate_20180216.img

I have questions:

  1. If I do apt-get update && apt-get upgrade, will it also update the dtb & Kodi ?
  2. If above update does not work, is there a trick to copy all Add-ons to the fresh install ?

Thank you

Share this post


Link to post
Share on other sites
On 14.04.2018 at 12:25 PM, Tido said:

I have installed some Add-ons to Kodi and I wanted to make use of the remote-control RC6 (Gateway). Reading in the main thread I found that due to dtb the remote will not work on my image. I have this running on eMMC: Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_mate_20180216.img

I have questions:

  1. If I do apt-get update && apt-get upgrade, will it also update the dtb & Kodi ?
  2. If above update does not work, is there a trick to copy all Add-ons to the fresh install ?

Thank you

The remote control requires a configuration file (which must be located in /boot/remote.conf). Commands do not update the kernel, dtb, and KODI.

Share this post


Link to post
Share on other sites
On 4/16/2018 at 10:47 AM, balbes150 said:

The remote control requires a configuration file (which must be located in /boot/remote.conf)

I know, I read that. As I wrote I have a Microsoft MCE-RC6 remote which is very common.

However, I read this:

For KODI & LibreELEC I read that the keymaps for this remote-control are already integrated, but my remote does not work.

 

What do you use in your image:

  1. LIRC where a separate program, lircd, decodes the IR signals ?
  2. Modern Linux kernels, like the ones used in LibreELEC, have built-in support for IR remotes ?

I found this for MCE-RC6  torvalds keymaps/rc-rc6-mce.c 

In which direction shall I search: KODI-Wiki   or   LibreELEC ??

Share this post


Link to post
Share on other sites

There is a great variety of different builds of KODI and Libreelec for different platforms (x86 , ARM, etc) and different models. This is a different system, description, for some not suitable to others. To operate your remote control, you need a settings file. See the example files (remote.conf) on a recorded medium. For KODI-17 from the composition of Armbian, the file must match the format of the driver amremote. For KODI-18, this is a different format (lirc).

Share this post


Link to post
Share on other sites

The service is running

Spoiler

 


root@amlogic:~# service amlogic-remotecfg status
 amlogic-remotecfg.service - Amlogic IR remote support
   Loaded: loaded (/usr/lib/systemd/system/amlogic-remotecfg.service; enabled; vendor preset: enabled)
   Active: active (exited) since Fri 2018-05-11 07:08:48 UTC; 4h 23min ago
  Process: 3218 ExecStart=/usr/lib/libreelec/remote-config (code=exited, status=0/SUCCESS)
 Main PID: 3218 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/amlogic-remotecfg.service

May 11 07:08:47 amlogic remote-config[3218]:         debug_enable = 0x0
May 11 07:08:47 amlogic remote-config[3218]:      fn_key_scancode = 27
May 11 07:08:47 amlogic remote-config[3218]:    left_key_scancode = 28
May 11 07:08:47 amlogic remote-config[3218]:   right_key_scancode = 72
May 11 07:08:47 amlogic remote-config[3218]:      up_key_scancode = 68
May 11 07:08:47 amlogic remote-config[3218]:    down_key_scancode = 29
May 11 07:08:47 amlogic remote-config[3218]:      ok_key_scancode = 92
May 11 07:08:47 amlogic remote-config[3218]:  pageup_key_scancode = 5
May 11 07:08:47 amlogic remote-config[3218]: pagedown_key_scancode = 89
May 11 07:08:48 amlogic systemd[1]: Started Amlogic IR remote support.

 

cat /proc/bus/input/devices

root@amlogic:~# cat /proc/bus/input/devices
I: Bus=0010 Vendor=0001 Product=0001 Version=0100
N: Name="aml_keypad"
P: Phys=keypad/input0
S: Sysfs=/devices/meson-remote.11/input/input0
U: Uniq=
H: Handlers=sysrq kbd mouse0 event0 
B: PROP=0
B: EV=f
B: KEY=7fffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff ffffffffffffffff fffffffffffffffe
B: REL=103
B: ABS=0

 

 

How do I find out if the software can talk to the IR-receiver ?

In the configuration file I saw these lines and I guess I have to adjust it to LePotato...

#	factory_code      each device has it's unique factory code. 
#			  pattern:custom_code(16bit)+index_code(16bit)
#			  example: 0xff000001 = 0xff00(custom cod)  0001 (index)

but how do I find this ?

 

Share this post


Link to post
Share on other sites

I have tried all (3) available in /boot/, I have renamed each to  /boot/remote.conf  one after the other, did a:
service amlogic-remotecfg stop

service amlogic-remotecfg start

klicked with the remote, nothing happend on the Monitor. Looked at  dmesg -c  nothing.

 

How can I test if the IR-Receiver works (devicetree activated?) ?

 

Edit:

I read in a WETEK forum about LG remote-control, so I grab my LG remote and try:

root@amlogic:~# dmesg 
[ 8082.947291] remote: Wrong custom code is 0xbf40fb04

but I wanted to use the mce.. mission impossible ?

Edited by Tido
LG remote works

Share this post


Link to post
Share on other sites

Hi @balbes150, I am running Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_mate_20180307.img

with this device tree: gxl_p212_2g_lepotato.dtb

 

Why is the System Load so high ?

Welcome to ARMBIAN 5.41 user-built Ubuntu 16.04.4 LTS 3.14.29   
System load:   1.26 1.18 1.10  	Up time:       2:41 hours		
Memory usage:  10 % of 1784MB 	IP:            192.168.11.10
CPU temp:      49°C           	
Usage of /:    10% of 29G    

 

With my the remote of my LG TV ( of 2011) I can use the navigation buttons (most japanese companies support NEC protocol, whereas RC-5 and RC-6 is from Philips):

Spoiler

factory_code	= 0xfb040001  
work_mode       = 0
repeat_enable   = 1
release_delay   = 150
debug_enable    = 1
reg_control     = 0xfbe40

key_begin
    0xca 116    ;POWER
    0x07 105    ;KEY_LEFT
    0x06 106    ;KEY_RIGHT
    0x40 103    ;KEY_UP
    0x41 108    ;KEY_DOWN
    0x44 28     ;KEY_ENTER
    0x5b 102    ;KEY_HOME
    0x09 113    ;KEY_MUTE
    0x03 114    ;KEY_VOLUMEDOWN
    0x02 115    ;KEY_VOLUMEUP
    0x28 14     ;KEY_BACKSPACE
    0x72 59     ;KEY_F1
    0x71 60     ;KEY_F2
    0x63 61     ;KEY_F3
    0x61 62     ;KEY_F4
    0x10 11     ;KEY_0
    0x11 2      ;KEY_1
    0x12 3      ;KEY_2
    0x13 4      ;KEY_3
    0x14 5      ;KEY_4
    0x15 6      ;KEY_5
    0x16 7      ;KEY_6
    0x17 8      ;KEY_7
    0x18 9      ;KEY_8
    0x19 10     ;KEY_9
    0xb0 164    ;KEY_PLAYPAUSE
    0xb1 128    ;KEY_STOP
    0x1e 0x16c  ;KEY_FAV
key_end

 

 

Edited by Tido
NEC, RC-6

Share this post


Link to post
Share on other sites
13 hours ago, Tido said:

I have renamed each to  /boot/remote.conf  one after the other, did a:

To operate the remote control, you need your own settings file. The image contains files for TV boxes remote control models with the specified names. They're not right for you. You need to create or find a settings file for your remote control model.

12 hours ago, Tido said:

Why is the System Load so high ? 

This is a special feature of this variant of the kernel (change in the driver settings for LE).

 

Have you tried the latest version (from the "no-mali" directory) with kernel 4.16 ? Does sound work on your model ?

Share this post


Link to post
Share on other sites
13 hours ago, balbes150 said:

Have you tried the latest version (from the "no-mali" directory) with kernel 4.16 ?

I have not, I am still on Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_mate_20180307.img.  no-mali is this good,  video needs VPU  or am I wrong ?

 

13 hours ago, balbes150 said:

Does sound work on your model ?

I tried Audio-Jack, doesn't work.  I want to try HDMI audio later.  I have now tested HDMI - when I navigate it makes the clicking sound = it works

 

How can I return from KODI to standard Mate desktop ?

Edited by Tido
sound via HDMI works

Share this post


Link to post
Share on other sites
On 5/12/2018 at 11:23 AM, Tido said:

How can I return from KODI to standard Mate desktop ?

 

The choice of shell to start (Mate\XFCE or KODI).

 

On the screen enter username and password (in lightdm) in the upper right corner of the screen there is a menu where you choose which GUI to run. The list will be three items (two rows with kodi) and the last line mate. Select mate (something opposite mate was the point), then enter the username and password. The system remembers the last selected mode. If at the next login or what not to choose in this menu, system at the entrance will trigger the option that was turning off in the previous session.

Share this post


Link to post
Share on other sites

after you didn't answer me for a bit of time I came up with the idea to search in this Thread, however I was looking for something like: Ctrl + Alt + Backspace   to restart X.

When I jump around too fast the audio hangs and won't stop to repeat the clicking-sound. Playing a movie or YouTube doesn't work then neither.

 

What is the difference between Mali-5, Mali-6, Mali-7  did you already explain that?

Share this post


Link to post
Share on other sites
19 hours ago, Tido said:

after you didn't answer me for a bit of time I came up with the idea to search in this Thread, however I was looking for something like: Ctrl + Alt + Backspace   to restart X.

When I jump around too fast the audio hangs and won't stop to repeat the clicking-sound. Playing a movie or YouTube doesn't work then neither.

 

What is the difference between Mali-5, Mali-6, Mali-7  did you already explain that?

These are different versions of KODI and different versions of libMali (5, 6, 7) or build without libMali .

Share this post


Link to post
Share on other sites

Sorry to revive this topic after many months, but are there recent instructions to copy Armbian to the eMMC?  When I boot with the eMMC installed, it boots into Android.  If I look at the SD card, I have 

ls -ld /boot
lrwxrwxrwx 1 root root   18 Aug 25 13:17 dtb -> dtb-4.18.5-meson64
drwxr-xr-x 3 root root 4096 Jul 24 12:06 dtb-4.14.57-meson64
drwxr-xr-x 3 root root 4096 Aug 25 13:17 dtb-4.18.5-meson64
lrwxrwxrwx 1 root root   19 Jul 24 12:06 dtb.old -> dtb-4.14.57-meson64

I don't see a dtb.img to remove.  How can I boot into armbian with the eMMC module installed?  

Share this post


Link to post
Share on other sites

@Tido, thanks.  I was hoping there were instructions that would let me work directly with Armbian.  I need to run a nightly kernel.  I am unsure whether I can intsall @Balbes150's image and then install a kernel on top of it (from eMMC) since it won't have the right dtb.  I don't suppose Balbes150 has instructions on builiding his kernel?  or is it all in the dtb and if I copy that from one of his images, it will be enough?  I'll give it a shot.

Share this post


Link to post
Share on other sites

Here is my current progress...

Note: I have not yet been able to boot directly from the emmc into Armbian.

 

I was not able to get balbes150's images to boot with emmc installed.  Not sure why, but it wasn't too interesting to me since I want to run a 4.17 kernel.

 

I was able to boot into a current armbian (via SSD) with the emmc module enabled via:

1) install armbian to an sd-card, boot and configure without emmc installed

2) connect a serial UART connecton to the UART pins on the le potato (baud 115200)

3) boot or reboot le-potato (still without emmc)

4) press enter several times in serial-console to enter u-boot prompt

5) install emmc module (while in u-boot prompt)

6) type 'run distro_bootcmd' in serial console to load armbian from sd-card

 

This at least gets me a current armbian env with the emmc available:

Device          Boot   Start      End  Sectors  Size Id Type
/dev/mmcblk0p1             0     8191     8192    4M 83 Linux
/dev/mmcblk0p2         73728   204799   131072   64M 83 Linux
/dev/mmcblk0p3        221184  1269759  1048576  512M 83 Linux
/dev/mmcblk0p4       1269760 25800703 24530944 11.7G  5 Extended
/dev/mmcblk0p5       1286144  1302527    16384    8M 83 Linux
/dev/mmcblk0p6       1318912  1384447    65536   32M 83 Linux
/dev/mmcblk0p7       1400832  1466367    65536   32M 83 Linux
/dev/mmcblk0p8       1482752  1499135    16384    8M 83 Linux
/dev/mmcblk0p9       1515520  1531903    16384    8M 83 Linux
/dev/mmcblk0p10      1548288  1613823    65536   32M 83 Linux
/dev/mmcblk0p11      1630208  1695743    65536   32M 83 Linux
/dev/mmcblk0p12      1712128  1777663    65536   32M 83 Linux
/dev/mmcblk0p13      1794048  5988351  4194304    2G 83 Linux
/dev/mmcblk0p14      6004736 30535679 24530944 11.7G 83 Linux

Looking at the u-boot code from armbian, I am not sure it will be able to boot emmc without modification.  It seems to only load from mmc or usb...I think we need to boot from emmc?  I have to play with it some more.  Alternatives are to try to use use the existing u-boot on the emmc, or to use balbes150's u-boot with a FAT fs...  I am currently going through the nand-sata-install script to make sure it isn't likley to break anything before I try it.

 

One thing I am happy to see...The EMMC is much faster than the fastest sd card I have. 

Comparison:

EMMC:
|      | Read(MB/s)|Write(MB/s)|
|------|-----------|-----------|
|Seq1M |     75.438|     41.317|
|Seq32M|     80.075|     43.023|
| 512K |     72.856|     39.066|
|   4K |     14.463|     15.634|

SD (Samsung Extreme 16GB)
|      | Read(MB/s)|Write(MB/s)|
|------|-----------|-----------|
|Seq1M |     21.873|     14.821|
|Seq32M|     21.917|     15.424|
| 512K |     21.121|     12.297|
|   4K |      7.578|      0.926|

Same SD card (Sandisk Extreme 16GB) in PC on USB3 port:
|      | Read(MB/s)|Write(MB/s)|
|------|-----------|-----------|
|Seq1M |     72.737|     48.762|
|Seq32M|     72.847|     49.757|
| 512K |     67.712|     32.398|
|   4K |      6.694|      0.750|

So we can see that the emmc provides massively improved sequential and random-access performance on the le potato.

 

Share this post


Link to post
Share on other sites
On 9/5/2018 at 8:40 AM, Tido said:

Balbes150 images offers dual boot

I guess you came across his first post: https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x/

Once you have multiboot, you can backup the eMMC (especially the dtb), then copy Balbes armbian on eMMC and now you can tweak it how you like it.

eMMC needs many partitions, I don't know why.

 

Share this post


Link to post
Share on other sites
9 hours ago, Tido said:

I guess you came across his first post: https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x/

Once you have multiboot, you can backup the eMMC (especially the dtb), then copy Balbes armbian on eMMC and now you can tweak it how you like it.

eMMC needs many partitions, I don't know why.

 

Thanks @Tido I did indeed miss that.  Thta would probably be the easiest way to get this working.  I, however, tend to prefer the hard way.  Balbes appears to be working with the legacy uboot shipped by Amlogic.  Armbian is using 2018.05 (probably soon to be 2018.07) which actually has mainline support for the le potato.  I'd much prefer to use the more modern version (that also doesn't require all those partitions).  I'm going to continue trying to figure out what that will take

 

Share this post


Link to post
Share on other sites

Thanks again @Tido.  I ended up using that image to install multiboot, which was indeed very helpful. While the install.sh script included won't work as is (need to change some paths since it is setup to install on mmc1), and the install.sh from 3.14 won't work with this image because the /dev paths are completely different, this was really helpful to understand how the boot process and upgrade works.

 

In the end, I didn't use Balbes's boot at all.  His multboot isn't compatible with stock Armbian, and whle it is probably possible to write an aml_autoscript which would work, I didn't bother.

 

Here is my process of installing a stock Armbian system on a Le Potato's EMMC.  The nand-sata-install almost works properly, I'm not sure if the issue is in u-boot or armbian, but I'll try to file a bug when I figure out where.  This process gives full access to the full EMMC (The legacy u-boot wastes ~3GB in random partitions).  Note that because these steps erase all of the partitions, it would be challenging to go back to Android in the future.

 

1) put Armbian official 'le potato' image on sd card
2) install sd card into le-potato and remove emmc
3) install UART onto 'le potato' and connect to PC @ 115200 baud
4) power up le potato
5) press enter several times in serial terminal to enter u-boot
6) install emmc
7) type 'run distro_bootcmd' in serial terminal
8) boot into Armbian...setup root and user, etc
9) sudo cfdisk /dev/mmcblk0
9a) remove all partitions.
9b) create a single linux partition (type 83) that fills the whole disk
9c) write changes
10) ls -l /dev/mmcblk0* and ensure you do not see mmcblk0p2-p14

10a) if you see any partitions (/dev/mmcblk0p2-p14) you need to reboot and go through steps 4-8 again
11) sudo nand-sata-install
11a) select emmc
11b) select ext4
11c) let the installation complete
11d) complete but DO NOT REBOOT
12) sudo mount /dev/mmcblk0p1 /mnt
13) sudo sh -c 'echo "bloader=ext4load mmc 1:1" >> /boot/armbianEnv.txt'
14) shutdown, remove sd card and reboot

 

steps 11d-13 are needed because u-boot 2018.05 sets 'bloader=ext4load mmc 0:1'  which forces booting the sdcard. This should ideally be calculated in either armbian's boot.scr or in u-boot itself

 

Share this post


Link to post
Share on other sites

Here is an alternative solution that doesn't require a UART...i didn't test these exact steps, but I believe they should work.  Again, note that step (5) will make it impossible to boot back to Android OR to mount Balbes's images onto EMMC

 

1) install Balbes's 5.59 debian-stretch-default onto USB/SD( it is important to use a 4.xx kernel for this method!): https://yadi.sk/d/pHxaRAs-tZiei/5.59/20180829

2) Follow his instructions to setup multiboot: https://forum.armbian.com/topic/2419-armbian-for-amlogic-s905-and-s905x/

3) Reboot into armbian

 

4) From armbian, download the official 'Le Potato image' ( You could also put this on a second USB drive and mount it in Armbian)

5) Copy the image onto EMMC: sudo dd if=<path to armbian.img> of=/dev/mmcblk0 bs=4096 status=progress

6) Fixup armbianEnv.txt:

6a) sudo mount /dev/mmcblk0p1 /mnt

6b) sudo sh -c 'echo "bloader=ext4load mmc 1:1" >> /boot/armbianEnv.txt'

7) remove USB/SD and reboot

 

Share this post


Link to post
Share on other sites

I recently purchased a Libre Compter AML-S905 SBC and  installed Armbian- 5.60 stable (stretch) with 4.18.8-meson64 kernel on both the SD card and a eMMC disk. I used armbian-config to copy the OS to the eMMC. After modification of armbianEnv.txt on the SD card, I can boot into the eMMC, but only with the SDcard installed. After reading several threads on u-boot and eMMC I am still somewhat confused. To investigate whether I have a bootloader on the eMMC disk, I dd-ed the first sectors of the eMMC to a file an compared it to /usr/lib/linux-u-boot-next-lepotato_5.6_arm64/u-boot.bin, and they look similar.

 

Then I tried to copy /usr/lib/linux-u-boot-next-lepotato_5.6_arm64/u-boot.bin to the eMMC disk, as shown in https://github.com/BayLibre/u-boot/tree/readme

dd if=u-boot.bin of=/dev/mmcblk0 bs=512 seek=1

But then the system did not boot either and my eMMC partition table was gone. Using testdisk, I could restore my partition table.

 

Now I am wondering how to get u-boot on my eMMC, and I have number of questions.

  • Can the u-boot provided with the last armbian images boot from a eMMC? (no)
  • Do I need the latest u-boot from github (https://github.com/BayLibre/u-boot/tree/readme) to get eMMC booting? I am not looking forward to setup cross compilation on my desktop...
  • Do I need multiboot or Balbes Debian image to proceed from where I am? I assume that I only need step 6 from the guide above, since I copied the official image using armbian-config.
  • Does step 5 also include the bootloader? If so, why doesn't armbian-config not does something similar to get a proper bootloader on the eMMC disk?
  • I don't understand 6 above. While running from SD card, the eMMC is mounted but armbinaEnv.txt from the SD card is modified.
  • Is there a working u-boot.bin that can be dd-ed to my eMMC?
  • Are there more steps required, e.g. compiling zimages or something to make sure u-boot can find the kernel?

Help is appreciated. I have been running linux for years at home and have done quite some playing with partitions and bootloaders, but this u-boot thing confuses me.

Share this post


Link to post
Share on other sites

So, I've been fighting with getting a working Armbian install on my eMMC for almost a week now. I should also mention I have a serial console hooked up, so I am working strictly over the serial debug console. I've ruled out power issues, and here's the problem I'm at now.

 

I used balbes' latest image to create a bootable SD card. I can boot with that card. I ended up only having success by using the nand-sata-install command once I had gotten booted into that version of armbian. I mounted the eMMC and verified the boot files, and then reboot without the SD card present in order to boot straight from eMMC. The kernel gets to remounting the root filesystem and just hangs. The last message is:

[    4.062163] [drm] Cannot find any crtc or sizes

It just sits there. If, at this point, I insert the SD card, the system sees it, and mounts that card as root and boot. So, my system is then running only on the SD card, again. I've tried a few things with changing the fstab on the emmc to use the /dev/mmcblk1p2 for root instead of LABEL= as well as for /boot, figuring it was that old bug that prevented mounting with labels. It's not that. I also tried changing the boot/uEnv.ini file to use the /dev/ device rather than the label, still no luck. It just will not mount the mmc as the root file system. Not sure what info is needed to proceed. I also gave the above bloader line a spin in armbianEnv.txt but it didn't help anything. Any one have any ideas here? Is there another file I need to modify to boot solely from the eMMC?

Share this post


Link to post
Share on other sites

This should just need a bootscript update to work properly under standard Armbian.  I ran nand-sata-install and the board boots, but the script isn't ready for it and tries to load everything from SD even though it doesn't exist.

 

[update] https://github.com/armbian/build/commit/cfd8a8956814a2f9da465769c1f9f5ad49e369cc

 

This boot script takes care of eMMC and has overlays baked in, that I need to experiment with/test.

 

        File size set to 102400 kB
        Record Size 4 kB
        Record Size 16 kB
        Record Size 512 kB
        Record Size 1024 kB
        Record Size 16384 kB
        Command line used: iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2
        Output is in kBytes/sec
        Time Resolution = 0.000001 seconds.
        Processor cache size set to 1024 kBytes.
        Processor cache line size set to 32 bytes.
        File stride size set to 17 * record size.
                                                              random    random     bkwd    record    stride
              kB  reclen    write  rewrite    read    reread    read     write     read   rewrite      read   fwrite frewrite    fread  freread
          102400       4    14931    15285    18479    21632    17644    13118
          102400      16    20817    25509    43118    43201    39345    23868
          102400     512    26357    26404    76260    76124    76281    26328
          102400    1024    27718    27917    77808    77832    77815    27793
          102400   16384    27825    28640    81196    81216    81233    28761

 

Share this post


Link to post
Share on other sites

Thanks for the update. I copied the file linked and pasted it into my emmc boot as boot.cmd, then ran mkimage to generate the scr. Unfortunately, I'm still getting the previous results. I then re-ran the nand-sata-install command to clear the emmc back to a default state before any of my tinkering, and tried again. Still stops at remounting root fs. Is there a direct link to an image for the version of armbian you are using here that I can plop onto my SD card to try booting from? I am currently using the images from balbes, and I don't know if that's configured differently. I'd like to just use whatever image you're reporting success with here.

Share this post


Link to post
Share on other sites
2 hours ago, sbc_chrisb said:

I am currently using the images from balbes, and I don't know if that's configured differently. I'd like to just use whatever image you're reporting success with here.

I am using the image family you would find on the Armbian download page, you are correct that the configuration of Balbes' images are different.  Whenever the next round of images are made this update will be included.

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
4 4