Important update:*****
As of mid/late 2014 A20-OLinuXino-MICRO board is supported by Arch Linux ARM developers/community
Please follow the new guide how to generate bootable image https://www.olimex.com/forum/index.php?topic=1856.msg15719#msg15719 (https://www.olimex.com/forum/index.php?topic=1856.msg15719#msg15719)*****
Hello,
I received my A20-OLinuXino-MICRO yesterday and I have to say I'm impressed!
However, I'm not into Debian, so I decided to try to build an ALARM image.
After spending several hours reading linux-sunxi site, downloading and compiling uboot, kernel, board fex file, modifying alarm rootfs, debugging uboot issues, etc... I finally managed to create a bootable Arch Linux ARM image 8)
Links for download:
Gzipped image (310 MB):
https://docs.google.com/file/d/0BwafTA6sZEvVWEFHQUd0cnlqRzA/edit?usp=sharing (https://docs.google.com/file/d/0BwafTA6sZEvVWEFHQUd0cnlqRzA/edit?usp=sharing)
md5sum of image (48 bytes):
https://docs.google.com/file/d/0BwafTA6sZEvVc3ZYd3Z2RUFRTEU/edit?usp=sharing (https://docs.google.com/file/d/0BwafTA6sZEvVc3ZYd3Z2RUFRTEU/edit?usp=sharing)
Instructions:
1. Download the 2 files.
2. Uncompress the alarm-a20.img.gz (gzip -d alarm-a20.img.gz).
3. Compare with the md5sum (md5sum -c alarm-a20.md5).
4. Write the image to an sd card (dd if=alarm-a20.img of='your_sd_card', where 'your_ssd_card' could be /dev/mmcblk0 or /dev/sdb). In Windows you can use Win32 disk imager.
5. Insert the SD card into the board, power it up and enjoy :)
Update: initial root password is root
Image highlights:
- linux kernel 3.4.43+ (linux-sunxi)
- systemd 204
- fits even on 1 GB SD card
- CLI only but you can install packages from the official repositories
- tons of kernel modules, exotic hardware support (in theory)
Note that I built it about 1 hour ago, I didn't test HDMI, wireless, GPIO ...
I'm also preparing instructions for building the image from scratch. Stay tuned :)
Update: Here is the promised guide:
http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ (http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/)
Hi
this is great, we just complete our new image with Kernel 3.4 and it have all peripherials working fine
I will blog the build instructions so you can include all GPIO, WIFI etc support in your ALARM image too!
Ooops, I forgot to write the root password for my ALARM image.
Initial root password is root.
Quote from: olimex on September 12, 2013, 05:14:54 PM
Hi
this is great, we just complete our new image with Kernel 3.4 and it have all peripherials working fine
I will blog the build instructions so you can include all GPIO, WIFI etc support in your ALARM image too!
When will you release these version?
Regards,
Pinnchus,
The promised guide for building your own ALARM image is here:
http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/ (http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/)
Hi thanks for your work and to share it with us ;-)
New Arch Linux ARM image (revision 2) for A20-OLinuXino-MICRO available:
Gzipped img (310 MB): https://docs.google.com/file/d/0BwafTA6sZEvVSVgyVU1ZMjZoclE/edit?usp=sharing (https://docs.google.com/file/d/0BwafTA6sZEvVSVgyVU1ZMjZoclE/edit?usp=sharing)
md5sum of img: https://docs.google.com/file/d/0BwafTA6sZEvVLTBmWlZ4NWdSSlE/edit?usp=sharing (https://docs.google.com/file/d/0BwafTA6sZEvVLTBmWlZ4NWdSSlE/edit?usp=sharing)
Highlights:
- linux kernel 3.4.61
- systemd 207
- used latest ALARM rootfs for sun7i (2013-10 from 28-Sep-2013)
credentials: root/root
Hi all,
I've just flashed the Arch image from this thread. Anyone who successfully got usb drives or higher display resolution (FullHD) to work ?
Arch as such is a blast, but without working usb/full hd, debian seems to be the more stable solution.
Cheers,
John
Perhaps because i'm quite new to the scene:
But the above wordpress quide doesn't load any video output buffers standard in the kernel.
Also sound and midi USB is disabled by default (and allot of other USB stuff)
To enable change the .config / DEFCONFIG file and rebuild uIMage.
I recommend that if something doesn't work, you start looking at the .config first.
Hello,
I installed on sd card the linux Kernel 3.4.3.43 on my A20
I got a problem with the net, it isn't possible to surf with browser (Iceweasel).
I also tryed to configure the ethernet card by typing on the terminal the following command:
ifconfig eth0 192.168.1.4 netmask 255.255.255.0 up
Unfortunatly doesn't work.
Could someone help me to make the ethernet port works so to surf with a browser?
Thanks a lot in advance!
Hi,
I installed the image and it is running fine. I also bought the 7" LCD display but
no way that i can get it working.
Can somebody provide a working FEX? I tried the one from de debian image but that one is not working.
[disp_init]
disp_init_enable = 1
disp_mode = 0
screen0_output_type = 1
screen0_output_mode = 4
screen1_output_type = 1
screen1_output_mode = 4
fb0_framebuffer_num = 2
fb0_format = 10
fb0_pixel_sequence = 0
fb0_scaler_mode_enable = 0
fb1_framebuffer_num = 2
fb1_format = 10
fb1_pixel_sequence = 0
fb1_scaler_mode_enable = 0
Regards,
Johan
Hi everyone,
I managed to build my own ArchLinux image too. However, I have some problems. First, as stated by other users, the display is not working (is anybody get something working ?). My disp_init on the .fex file looks like this (it's from Olimex) :
[disp_init]
disp_init_enable = 1
disp_mode = 0
screen0_output_type = 3
screen0_output_mode = 4
screen1_output_type = 3
screen1_output_mode = 4
fb0_framebuffer_num = 2
fb0_format = 10
fb0_pixel_sequence = 0
fb0_scaler_mode_enable = 0
fb1_framebuffer_num = 2
fb1_format = 10
fb1_pixel_sequence = 0
fb1_scaler_mode_enable = 0
lcd0_backlight = 197
lcd1_backlight = 197
lcd0_bright = 50
lcd0_contrast = 50
lcd0_saturation = 57
lcd0_hue = 50
lcd1_bright = 50
lcd1_contrast = 50
lcd1_saturation = 57
lcd1_hue = 50Second, I plugged a PL2303 serial to usb converter onto the UART so I could watch the boot process but I can't get any login screen. I can see that the boot process throw some errors about starting the ttyS0 service but there isn't any other informations. Here are the errors I got :
Quotejanv. 01 01:00:14 alarm systemd[1]: Starting OpenSSH Daemon...
janv. 01 01:00:14 alarm systemd[1]: sshd.service start request repeated too quickly, refusing to start.
janv. 01 01:00:14 alarm systemd[1]: Failed to start OpenSSH Daemon.
janv. 01 01:00:14 alarm systemd[1]: Unit sshd.service entered failed state.
janv. 01 01:01:33 alarm systemd[1]: Job sys-subsystem-net-devices-eth0.device/start timed out.
janv. 01 01:01:33 alarm systemd[1]: Timed out waiting for device sys-subsystem-net-devices-eth0.device.
janv. 01 01:01:33 alarm systemd[1]: Dependency failed for Automatic wired network connection using netctl profiles.
janv. 01 01:01:33 alarm systemd[1]: Job dev-ttyS0.device/start timed out.
janv. 01 01:01:33 alarm systemd[1]: Timed out waiting for device dev-ttyS0.device.
janv. 01 01:01:33 alarm systemd[1]: Dependency failed for Serial Getty on ttyS0.
The errors related to ssh are:
Quotejanv. 01 01:00:14 alarm sshd[111]: Could not load host key: /etc/ssh/ssh_host_rsa_key
janv. 01 01:00:14 alarm sshd[111]: Could not load host key: /etc/ssh/ssh_host_dsa_key
janv. 01 01:00:14 alarm sshd[111]: Could not load host key: /etc/ssh/ssh_host_ecdsa_key
janv. 01 01:00:14 alarm sshd[111]: Could not load host key: /etc/ssh/ssh_host_ed25519_key
The errors related to the network could be a bad configuration however I'm not using it for now so it's not important to me.
I should add that the boot process finish with these lines:
Quotejanv. 01 01:01:33 alarm systemd[1]: Starting Login Prompts.
janv. 01 01:01:33 alarm systemd[1]: Reached target Login Prompts.
janv. 01 01:01:33 alarm systemd[1]: Starting Multi-User System.
janv. 01 01:01:33 alarm systemd[1]: Reached target Multi-User System.
janv. 01 01:01:33 alarm systemd[1]: Starting Graphical Interface.
janv. 01 01:01:33 alarm systemd[1]: Reached target Graphical Interface.
janv. 01 01:01:33 alarm systemd[1]: Startup finished in 5.600s (kernel) + 1min 31.012s (userspace) = 1min 36.613s.
janv. 01 01:15:03 alarm systemd[1]: Starting Cleanup of Temporary Directories...
janv. 01 01:15:03 alarm systemd[1]: Started Cleanup of Temporary Directories.
Last post is from May, it seems that there isn't a lot of people trying to make ArchLinux works on A20. C'mon! ArchLinux is the best distribution ever. I think that we could get it working as good as the official debian image. Let's take the challenge ;)
Today I used bin2fex to extract the fex file from the script.bin shared by Olimex on the article on how to build the Debian image. What I can tell it's that it is a little bit (and not only a little) different.
Here is the disp_init part for example:
[disp_init]
disp_init_enable = 1
disp_mode = 0
screen0_output_type = 3
screen0_output_mode = 5
screen1_output_type = 1
screen1_output_mode = 4
fb0_framebuffer_num = 2
fb0_format = 10
fb0_pixel_sequence = 0
fb0_scaler_mode_enable = 0
fb0_width = 0
fb0_height = 0
fb1_framebuffer_num = 2
fb1_format = 10
fb1_pixel_sequence = 0
fb1_scaler_mode_enable = 0
fb1_width = 0
fb1_height = 0
lcd0_backlight = 250
lcd1_backlight = 100
lcd0_bright = 50
lcd0_contrast = 50
lcd0_saturation = 57
lcd0_hue = 50
lcd1_bright = 50
lcd1_contrast = 50
lcd1_saturation = 57
lcd1_hue = 50
I'll try it later. I'll keep you in touch.
EDIT: I've just tried with the script.bin given by Olimex. I still get the exactly same issues. I'm stuck and can't access a login prompt. Too bad for me, I could try things if I could get this login prompt. Here is a pastebin of the boot process (http://sebsauvage.net/paste/?0d45ac083bad747b#0juNMBRu5KuXvlHFH0sRPr6kRAMvHTRIYeeHtjmfxYQ=). This pastebin will expire in one month.
Quote from: Shakipu on June 14, 2014, 07:03:52 PM
Today I used bin2fex to extract the fex file from the script.bin shared by Olimex on the article on how to build the Debian image. What I can tell it's that it is a little bit (and not only a little) different.
To active the 7" Display you just have to exchange the following line in step 3:
(http://alarma20.wordpress.com/2013/09/13/howto-build-arch-linux-arm-for-a20-olinuxino-micro/)
wget https://github.com/linux-sunxi/sunxi-boards/raw/master/sys_config/a20/a20-olinuxino_micro.fex
by
wget https://raw.githubusercontent.com/linux-sunxi/sunxi-boards/master/sys_config/a20/a20-olinuxino_micro-lcd7.fex
the rest should work out of the box. If it doesn´t then it is more like a kernel or X server issue.
I haven´t tried it myself, but maybe I have a little bit of time next week to give it a try.
Quote from: Shakipu on June 14, 2014, 07:03:52 PM
Today I used bin2fex to extract the fex file from the script.bin shared by Olimex on the article on how to build the Debian image. What I can tell it's that it is a little bit (and not only a little) different.
I'll try it later. I'll keep you in touch.
Hey, I built the image today. I followed the instructions from the guide but I used the defconfig file from the original guide for Debian ("Building the Ultimate Debian..."). I made one modification and that was to enable FHANDLE,
CONFIG_FHANDLE=y, on line 58 under general setup. I found out earlier that newer systemd requires that, otherwise you will get stuck with those devices timing out and not be able to login via serial:
[ TIME ] Timed out waiting for device sys-subsystem-net-devices-eth0.device.
[DEPEND] Dependency failed for Automatic wired network connec...etctl profiles.
[ TIME ] Timed out waiting for device dev-ttyS0.device.
[DEPEND] Dependency failed for Serial Getty on ttyS0.Currently serial and ethernet are all I have working (no video/hdmi) so I am working on getting the mali drivers from the AUR, xf86-video-sunxifb-git
I will keep posted my findings, goodluck.
Edit: fixed my video/hdmi issue; modules weren't correctly compiling.
Edit2: using the a20 lcd7 fex and following the guide here: https://www.olimex.com/forum/index.php?topic=1743.0
I managed to get touchscreen working. I used sun4i-ts as the module as sunxi-ts does not exist for me.
Your image has FAT first partition or EXT4? In new uimage, we could use ext4. In official installation, for example Cubieboard2 (http://archlinuxarm.org/platforms/armv7/allwinner/cubieboard-2), it uses FAT
Thanks,
After installing your img, after doing `pacman -Syu` I get that Olimex does not boot.
Latest systemd requires special kernel modification in order to boot. As I'm using my OLinuXino only headless I tried the mainline kernel (3.16 and 3.17-rc) and both work very good on my board. If I have enough free time I'll prepare instructions for building Arch Linux ARM image for A20-OLinuXino using vanilla kernel from kernel.org
The problem is that network is not boot. The system itself boots but not the network. I haave no screen so I NEED that network works.
Why don't you put efforts to support the archlinuxarm official distro?
Quote from: xanb on September 23, 2014, 06:06:40 PM
The problem is that network is not boot. The system itself boots but not the network. I haave no screen so I NEED that network works.
Why don't you put efforts to support the archlinuxarm official distro?
I don't know why Arch Linux ARM developers don't support Allwineer based OLinuXino boards.
As you can see list of supported boards is not so small:
http://archlinuxarm.org/platforms/armv7/allwinner (http://archlinuxarm.org/platforms/armv7/allwinner)
Probably they need to receive free boards from Olimex in order to officially support them.
Better ask in their forums for more info.
The main difference between all those boards is the u-boot bootloader config, so if you compile one for OLinuXino and replace the Cubieboard's in the official ALARM image it will most probably run w/o issues.
Although no official support is provided for AllWinnner based OLinuXino boards in Arch Linux ARM, it seems that there is at least semi-official support ;).
ALARM developers provide generic AllWinner sun7i (A20), sun4i (A10) and sun5i (A13, A10s) rootfs and kernel.
There are also u-boot pacman packages for many boards including A20-OLinuXino-MICRO located here:
http://os.archlinuxarm.org/armv7h/alarm/ (http://os.archlinuxarm.org/armv7h/alarm/)
So here is a simplified version howto install Arch Linux ARM on your A20-OLinuXino-MICRO board:
Follow the official guide for Cubieboard 2 (Installation tab):
http://archlinuxarm.org/platforms/armv7/allwinner/cubieboard-2 (http://archlinuxarm.org/platforms/armv7/allwinner/cubieboard-2)
Execute steps 1-4.
Download u-boot package for A20-OLinuXino-MICRO, current one is available here:
http://os.archlinuxarm.org/armv7h/alarm/uboot-a20-olinuxino-micro-2014.04-9-armv7h.pkg.tar.xz (http://os.archlinuxarm.org/armv7h/alarm/uboot-a20-olinuxino-micro-2014.04-9-armv7h.pkg.tar.xz)
Open it with Archive program such as Archive Manager, Ark, etc. Go to boot directory and extract the 3 files (uEnv.txt, script.bin, u-boot-sunxi-wth-spl.bin) on mnt/boot replacing the Cubieboard ones.
Proceed with steps 5-7 from Cubieboard2 guide (except that you need 12V power supply)
That's it
Yes, it works, but but `uboot-cubieboard2` in the ignore list of packages of pacman.conf. Else you can say "no" to this question everytime:
(14/14) upgrading uboot-cubieboard2 [##########################################] 100%
A new U-Boot version needs to be flashed onto /dev/mmcblk0.
Do you want to do this now? [y|N]
n
You can do this later by running:
# dd if=/boot/u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 bs=1024 seek=8
You could circumvent it, installing uboot-a20-olinuxino-micro:
# pacman -Si uboot-a20-olinuxino-micro
Repository : alarm
Name : uboot-a20-olinuxino-micro
Version : 2014.04-10
Description : U-Boot for A20 OLinuXino Micro
Architecture : armv7h
URL : https://github.com/linux-sunxi/u-boot-sunxi
Licenses : GPL
Groups : None
Provides : uboot-sunxi
Depends On : None
Optional Deps : None
Conflicts With : uboot-sunxi
Replaces : None
Download Size : 107.60 KiB
Installed Size : 318.00 KiB
Packager : Arch Linux ARM Build System <builder+xu6@archlinuxarm.org>
Build Date : Sat Oct 4 18:36:04 2014
Validated By : MD5 Sum SHA256 Sum Signature
[root@alarm ~]# pacman -S uboot-a20-olinuxino-micro
resolving dependencies...
looking for inter-conflicts...
:: uboot-a20-olinuxino-micro and uboot-cubieboard2 are in conflict (uboot-sunxi). Remove uboot-cubieboard2? [y/N] y
Packages (2): uboot-cubieboard2-2014.04-10 [removal] uboot-a20-olinuxino-micro-2014.04-10
Total Download Size: 0.11 MiB
Total Installed Size: 0.31 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages ...
uboot-a20-olinuxino-micro-2014.04-10-armv7h 107.6 KiB 262K/s 00:00 [##########################################] 100%
(1/1) checking keys in keyring [##########################################] 100%
(1/1) checking package integrity [##########################################] 100%
(1/1) loading package files [##########################################] 100%
(1/1) checking for file conflicts [##########################################] 100%
(2/2) checking available disk space [##########################################] 100%
(1/1) removing uboot-cubieboard2 [##########################################] 100%
(1/1) installing uboot-a20-olinuxino-micro [##########################################] 100%
A new U-Boot version needs to be flashed onto /dev/mmcblk0.
Do you want to do this now? [y|N]
y
258+1 records in
258+1 records out
264252 bytes (264 kB) copied, 0.00612632 s, 43.1 MB/s
[root@alarm ~]# nano /etc/pacman.conf
Following your instructions, I get empty /boot/uEnv.txt. How can I pass kernel parameters to that?
Could I simply pass extraargs directly?
extraargs=rootwait sunxi_g2d_mem_reserve=0 sunxi_ve_mem_reserve=0 sunxi_no_mali_mem_reserve
ipv6.disable=1 ethaddr=00:CE:39:B7:74:4E
without
boot_mmc=fatload mmc 0 0x43000000 ${fexfile}; fatload mmc 0 0x48000000 ${kernel}; bootm 0x48000000
What's the meaning of these?
Thanks,
google gave me http://linux-sunxi.org/UEnv.txt as first item
John
Quote from: JohnS on November 20, 2014, 12:34:02 PM
google gave me http://linux-sunxi.org/UEnv.txt as first item
John
John, I found this already. But it's useless information.
By the other hand, the boot process ignores the uEnv.txt information in my case. If I put
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rootwait panic=10 ${extra}
ext2load mmc 0 0x43000000 script.bin
ext2load mmc 0 0x48000000 uImage
bootm 0x48000000
extraargs=rootwait ipv6.disable=1
then dmesg shows me it ignores me. Why? ext2load? What's that? ext4load exists? A lot of info is missing....
I don't understand you.
John
Quote from: JohnS on November 23, 2014, 05:36:41 PM
I don't understand you.
John
Contents in uEnv.txt does not take into account (dmesg does not show those)
Sounds like you're using it wrongly.
I see others have posted suggestions which also will work if used correctly. Pick one and persevere?
John
Quote from: JohnS on November 24, 2014, 12:11:37 PM
Sounds like you're using it wrongly.
I see others have posted suggestions which also will work if used correctly. Pick one and persevere?
John
This is why I posted here. Can you be more specific please.
How?
Many details have been posted but few from you.
John
Quote from: JohnS on November 24, 2014, 02:33:00 PM
How?
Many details have been posted but few from you.
John
Dead road. No constructive answer to my problems. I try to find the solutions.... If I can't see them, can you point where there are and just to say that there are.
To me you need to follow previous ideas more than you have and see why things don't work or do what you want. No-one else probably wants exactly what you do so you have to find how to make what you want or else adopt what others want.
These are dev boards and you're doing bleeding edge stuff...
If you don't want grief, go with something that's known to work.
John
I only found this:
[http://archlinuxarm.org/forum/viewtopic.php?f=45&t=6743]
http://archlinuxarm.org/forum/viewtopic.php?f=45&t=5995&p=33791&hilit=wandboard#p33791
But not useful completely
Quote from: Aaron on March 29, 2014, 11:03:39 PM
I also tryed to configure the ethernet card by typing on the terminal the following command:
ifconfig eth0 192.168.1.4 netmask 255.255.255.0 up
Unfortunatly doesn't work.
You have to se the default route to your gateway, i.e. your router. For example, if you router has IP adress 192.168.1.1 (and very probably has), you must type also:
route add default gw 192.168.1.1And unless you have your nameservers preconfigured, you need also to set them. If your router works as DNS relay, you can try
echo "nameserver 192.168.1.1" > /etc/resolv.confOr you can use a Googles's public nameserver with easy-to-remeber IP adress 8.8.8.8:
echo "nameserver 8.8.8.8" > /etc/resolv.conf
hi all,
just tried the method posted by progmetalbg for running the cubieboard image on olinuxino, but I cannot find any new machine on the dhcp list of my router. I cannot see anything from hdmi, either. Should I see something? or maybe on the VGA port? how's u-boot configured in that one?
is it correct that uEnv.txt is blank?
It is hard to troubleshoot without USB Serial cable like this one sold by Olimex: https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/ (https://www.olimex.com/Products/Components/Cables/USB-Serial-Cable/USB-Serial-Cable-F/)
Do other Linux images provided by Olimex or other users boot on your board?
At least xanb reported that this method for creating bootable uSD card with Arch Linux ARM works for him.
uEnv.txt can be blank, it is not a problem.
Hi progmetalbg, thanks for your answer.
I used the debian distribution without problems in the past (but the image was too big to fit in a 4GB uSD, the only one that I have around now, and I prefer using arch linux).
I have some minimus AVR's lying around, I should be able to turn one of them in a usb to serial device. Then I'll come back with some useful information ;)
EDIT: nevermind, I got it working! I followed the steps again and everything went well. I think the last time I lost some steps at the end, maybe u-boot was not installed correctly. Thanks again!
Hello,
can i use this guide to install arch linux on a20-lime? If i understand it well, i need to change version of uboot - but i cant find a20-lime version of u-boot.
Thx for help.
Hello,
Try the prebuilt u-boot image archive from linux-sunxi:
http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi/u-boot-sunxi-latest/u-boot-sunxi-a20-olinuxino-lime.tar.xz (http://dl.linux-sunxi.org/nightly/u-boot-sunxi/u-boot-sunxi/u-boot-sunxi-latest/u-boot-sunxi-a20-olinuxino-lime.tar.xz)
or compile u-boot yourself follwing this guide: http://linux-sunxi.org/U-boot#Compile_U-Boot (http://linux-sunxi.org/U-boot#Compile_U-Boot)
I'm using the weekend to set up a streaming server with mopidy, so I can hook up my olinuxino to the speakers and control it via my laptop/smartphone. but alsa cannot detect any soundcard.
Is there an audio driver in the kernel? how is it called?
I don't have experience with sound on A20-OLinuXino, but you can check this wiki page http://linux-sunxi.org/Sound (http://linux-sunxi.org/Sound). If you don't find solution for your problem you can ask also in Arch Linux ARM forum http://archlinuxarm.org/forum/viewforum.php?f=33 (http://archlinuxarm.org/forum/viewforum.php?f=33)
Quote from: progmetalbg on December 20, 2014, 01:30:34 PM
I don't have experience with sound on A20-OLinuXino, but you can check this wiki page http://linux-sunxi.org/Sound (http://linux-sunxi.org/Sound). If you don't find solution for your problem you can ask also in Arch Linux ARM forum http://archlinuxarm.org/forum/viewforum.php?f=33 (http://archlinuxarm.org/forum/viewforum.php?f=33)
thanks for the quick response.
I always forget to add the user to the audio group. Audio is fine now!
listening to spotify (premium) from olinuxino and controlling it on my android :)
Hey there, I'm back!
I'm running succesfully arch on my olinuxino for some days, but now I want to change some things in my script.bin.
I've grabbed this fex file (https://github.com/linux-sunxi/sunxi-boards/raw/master/sys_config/a20/a20-olinuxino_micro.fex) and edited it a bit, then ran fex2bin and used the same dd command of the cubieboard guide to write it on the first part of the SD, but at reboot I got to the same state I was the first time I asked for help (basically olinuxino doesn't find the script.bin and doesn't output anything, even via serial interface).
So I tried to run bin2fex using the script.bin of the guide (the olinuxino one), but I get the following:
# bin2fex u-boot-sunxi-with-spl.bin script.fex
fexc-bin: u-boot-sunxi-with-spl.bin: version: 1313818469.810828334.1334599999
fexc-bin: u-boot-sunxi-with-spl.bin: size: 264252 (-369098746 sections)
E: fexc-bin: Malformed data: version 1313818469.810828334.1334599999.
do you have any hint to successfully edit the bin file?
Thanks for the attention!
Hi sanzoghenzo,
Correct commands are:
$ bin2fex script.bin script.fex
$ fex2bin script.fex script.binU-boot binary u-boot-sunxi-with-spl.bin is different than script.bin
In /boot you should have:
- uImage - Linux kernel
- u-boot-sunxi-with-spl.bin - compiled u-boot
- script.bin - binary version of script.fex
- uEnv.txt or boot.scr - not really needed but useful for specifying additional kernel parameters at boot.
Quote from: progmetalbg on January 03, 2015, 11:01:15 AM
Hi sanzoghenzo,
..
U-boot binary u-boot-sunxi-with-spl.bin is different than script.bin
In /boot you should have:
- uImage - Linux kernel
- u-boot-sunxi-with-spl.bin - compiled u-boot
- script.bin - binary version of script.fex
- uEnv.txt or boot.scr - not really needed but useful for specifying additional kernel parameters at boot.
Thanks progmetalbg, that's what I suspected, but ten I tried to move the script.bin file away from boot an everything worked, so I assumed it was useless.
Now I get that the compiled u-boot has a default config that is overridden by /boot/script.bin
Now that my script.bin is loaded I can test the dht22 module by hhornbacher :)
Thanks again and happy new year!