Jump to content

Search the Community

Showing results for tags 'micro'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware (WIP)
    • News
    • Odroid M1
    • ROCK 5B
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Unmaintained (CSC/EOL/TVB) / Other
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







  1. Dear community, I am experimenting with MangoPi board, trying to communicate with the CC2530 Zigbee board . To do so, I need an available UART port, the UART0 (/dev/ttyS0, pins 8 and 10) seems to be occupied by the console, but there should be two other UARTs according to the schematic. Some info: pi@nezha:~$ uname -a Linux nezha 5.19.0-rc1-d1 #trunk Fri Jul 22 12:44:22 MSK 2022 riscv64 riscv64 riscv64 GNU/Linux pi@nezha:~$ setserial -g /dev/ttyS* /dev/ttyS0: Permission denied /dev/ttyS2, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS3, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS4, UART: unknown, Port: 0x0000, IRQ: 0 /dev/ttyS5, UART: unknown, Port: 0x0000, IRQ: 0 pi@nezha:~$ dmesg|grep tty [ 0.000000] Kernel command line: root=UUID=09392a76-5b44-4ed0-b8c1-ea71be0c5a91 console=ttyS0,115200n8 cons ole=tty0 earlycon=sbi cma=96M rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck. repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian [ 0.022550] printk: console [tty0] enabled [ 0.036087] printk: console [tty0] printing thread started [ 2.054357] printk: console [ttyS0] disabled [ 2.074657] 2500000.serial: ttyS0 at MMIO 0x2500000 (irq = 207, base_baud = 1500000) is a 16550A [ 2.074952] printk: console [ttyS0] enabled [ 2.097185] 2500400.serial: ttyS1 at MMIO 0x2500400 (irq = 208, base_baud = 1500000) is a 16550A [ 2.097219] printk: console [ttyS0] printing thread started [ 2.121099] serial serial0: tty port ttyS1 registered [ 12.144928] systemd[1]: Created slice Slice /system/serial-getty. [ 18.309394] systemd[1]: Found device /dev/ttyS0. pi@nezha:~$ ls -l /boot total 36312 -rwxr-xr-x 1 root root 64 Dec 23 21:18 armbianEnv.txt -rwxr-xr-x 1 root root 38518 Jul 22 10:21 boot.bmp -rwxr-xr-x 1 root root 173018 Jul 22 09:44 config-5.19.0-rc1-d1 drwxr-xr-x 3 root root 4096 Jul 22 10:20 dtb drwxr-xr-x 2 root root 4096 Jul 22 10:19 extlinux -rwxr-xr-x 1 root root 8399919 Jul 22 09:44 Image -rwxr-xr-x 1 root root 5087353 Jul 22 09:44 System.map-5.19.0-rc1-d1 -rwxr-xr-x 1 root root 15056913 Jul 22 10:24 uInitrd -rwxr-xr-x 1 root root 8399919 Jul 22 09:44 vmlinuz-5.19.0-rc1-d1 The usual approach seems to be using the armbian-config utlity, unfortunately, the utility does not allow configuring the hardware in the system branch. How do I enable the UART1? I tried to create the /boot/armbianEnv.txt file as follows: pi@nezha:~$ cat /boot/armbianEnv.txt overlays=uart1 and the /dev/ttyS1 seems to be created (?) but nothing to be seen in /dev/ttyS* pi@nezha:~$ dmesg|grep ttyS1 [ 2.097185] 2500400.serial: ttyS1 at MMIO 0x2500400 (irq = 208, base_baud = 1500000) is a 16550A [ 2.121099] serial serial0: tty port ttyS1 registered pi@nezha:~$ ls -l /dev/ttyS* crw--w---- 1 root tty 4, 64 Dec 23 21:18 /dev/ttyS0 crw-rw---- 1 root dialout 4, 66 Dec 23 21:18 /dev/ttyS2 crw-rw---- 1 root dialout 4, 67 Dec 23 21:18 /dev/ttyS3 crw-rw---- 1 root dialout 4, 68 Dec 23 21:18 /dev/ttyS4 crw-rw---- 1 root dialout 4, 69 Dec 23 21:18 /dev/ttyS5 Can somebody help please? I understand the MangoPi is fairly exotic board, but it's lovely RISC5 and we live in times of silicon shortage, so... In ideal case, I'd like to swap UART0 and UART1 to get my RX/TX on pins 8 and 10, but enabling UART1 will make me happy as well Apologies for the tag, the MangoPi does not seem to be very popular here, yet. Thank you, JP
  2. I am really confused about how to connect an LVDS monitor to the board. We used 3.x legacy kernel and used a .fex file for this in the past. But it is time to move to mainline, and it is confusing me. Since LVDS is not plug and play, we need to tell the parameters of the screen somehow. That is clear. I found several ways of pushing parameters to the system: 1. Compile into kernel 2. Compile into U-boot 3. Device Tree 4. Device Tree Overlay 5. Kernel command line According to these articles i have to compile them into U-boot: https://forum.armbian.com/topic/1905-enabling-lcd-in-u-boot-kernel-472/ http://linux-sunxi.org/LCD But it seems to me that it is a step backwards compared to .fex files. (and I have not figured out how to recompile U-boot in armbian yet) I found a commit, which states that there is some support for LVDS on A20s: https://github.com/torvalds/linux/commit/564c4815074291c40a584b1b05da3732beac990c#diff-ea438ea3ad237808b1c56c9c6ca647fe This suggest that i could somehow use Device Tree. Which i guess would be more future proof, but i do not know how to tell the exact parameters of the screen. Also i need to set the brightness, and turn off the monitor sometimes, how do I do that nowadays?
  3. Hi, my OLIMEX micro crashes recently quite often. Even thoug I upgrade to the latest version: "Welcome to ARMBIAN 5.60 stable Debian GNU/Linux 9 (stretch) 4.19.62-sunxi " I was able to catch this trace, any advise? Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21927.933087] Internal error: Oops: 80000005 [#1] SMP THUMB2 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.107488] Process dockerd (pid: 1813, stack limit = 0x95696597) Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.118470] Stack: (0xdc807dc8 to 0xdc808000) Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.127794] 7dc0: 00000005 00000000 00000000 00000000 00000000 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.141224] 7de0: dc806000 dc807e18 00000000 dc807f70 ffffe000 c0e04d48 00000000 c0180bc1 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.154775] 7e00: dc807e14 c0133c6f 00000000 dc807f70 ee2a6800 ef210280 d8433e19 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.168461] 7e20: 00000000 00000000 960fe839 000013ff 960f24e9 000013ff c01720cd ef6c87c0 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.182318] 7e40: 00000001 00000000 ee2a6800 dc807f10 ef6c87c0 00000064 dc807e58 dc807e58 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.196298] 7e60: dc807e60 dc807e60 ee2a6800 00000000 03da4000 c9c5f400 00000570 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.210416] 7e80: 00000000 00000000 ffffffff 4faf8638 dc807f78 00000000 00000000 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.224669] 7ea0: 00000000 03da4570 00000000 00000051 c0e04d48 c018240f ffffffff 000013f1 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.239054] 7ec0: ef6e1c40 7fffffff ef6da858 ef6da830 ef6da808 c017e779 00000000 7fffffff Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.253747] 7ee0: 00000000 4faf8638 00011170 00000000 c0e04d48 0000c350 0000c350 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.268537] 7f00: 00000001 c01726f3 ee2a6800 00000000 dc807f10 ef6c8aa0 00000000 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.283361] 7f20: 9dc4e603 000013f1 9dc422b3 c0173081 c01720cd 4faf8638 00000000 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.298301] 7f40: c0e04d48 00000000 00000080 03da4570 00000000 00000051 03d3e738 c0182db1 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.313395] 7f60: 00000000 00000000 ffffffff 000000a2 960f24e9 000013ff 00000000 0000003c Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.328626] 7f80: 00000000 4faf8638 00000000 00000000 00000000 000000f0 c0101224 dc806000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.343986] 7fa0: 000000f0 c0101001 00000000 00000000 03da4570 00000080 00000000 a6895c84 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.359470] 7fc0: 00000000 00000000 00000000 000000f0 3b9aca00 00000000 05000540 03d3e738 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.375179] 7fe0: 000f2be8 a6895c64 008e1208 009172f8 a0070010 03da4570 00000000 00000000 Message from syslogd@micro at Aug 4 16:45:35 ... kernel:[21928.391251] Code: bad PC value ==========================armbainmonitor.log ================================= armbianmonitor.log
  4. Hi folks, I'd like to build a simple rs485 interface onto an A20-OLinuxino-Micro board. Therefore I was looking into utilizing one of the UARTs (6 or 7) on EXT1 or EXT2, add an external driver chip to it and 'fork' the according kernel module to implement support for switching send/receive with the RTS line. While that seemed to be an easy approach, I already got stuck with the basics. :-( dmesg shows me [ 2.822776] printk: console [ttyS0] disabled [ 2.842962] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 53, base_baud = 1500000) is a U6_16550A [ 2.843045] printk: console [ttyS0] enabled [ 2.866650] 1c29800.serial: ttyS1 at MMIO 0x1c29800 (irq = 54, base_baud = 1500000) is a U6_16550A [ 2.889933] 1c29c00.serial: ttyS2 at MMIO 0x1c29c00 (irq = 55, base_baud = 1500000) is a U6_16550A that during the boot process, the kernel seems to 'find' an initialize UART0 (ttyS0 on 0x1c28000), UART6 (ttyS1 on 0x1c29800) and UART7 (ttyS2 on 0x1c29c00). Nevertheless, if I look into sysfs # find /sys/devices/ -name 'ttyS*' /sys/devices/platform/soc/1c28000,serial/tty/ttyS0 /sys/devices/platform/soc/1c29c00,serial/tty/ttyS2 /sys/devices/platform/soc/1c29800,serial/tty/ttyS1 /sys/devices/platform/serial8250/tty/ttyS6 /sys/devices/platform/serial8250/tty/ttyS4 /sys/devices/platform/serial8250/tty/ttyS7 /sys/devices/platform/serial8250/tty/ttyS5 /sys/devices/platform/serial8250/tty/ttyS3 I see that all the other UARTs are also already recognized. How can I find out - which module/driver is loaded/used to access ttyS0, ttyS1 and ttyS2 - if ttyS3 - ttyS7 are 'active' and which module/driver was used - how to prevent the kernel from automatically loading a module for an 'active' ttySx ? Cheers, Klaus
  5. Hi folks, is there a reason behind the Olimex Micro board being listed as "SUPPORT ENDED (EOS)" on the armbian web site? Cheers, Klaus
  6. Hello, I would like to download the Armbian Buster image. This is not possible due to missing links. The Bionic is download link is working though. Sheers
  7. hi there, Recently there was an update for all Olimex boards with A20. Now we have one image for all the boards and it includes mainline kernel which is cool. I checked here and took the image from here. Now after a while I got strange error and wanted to check with you if you can share an opinion what this could be: [32673.051479] Unable to handle kernel NULL pointer dereference at virtual address 0000 [32673.060027] pgd = 9d6652ac [32673.062884] [00000000] *pgd=00000000 [32673.066666] Internal error: Oops: 5 [#1] SMP THUMB2 [32673.071795] Modules linked in: joydev input_leds ipt_MASQUERADE nf_conntrack_netlink iptable_nat nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack nf_netfilter bridge stp llc cifs ccm fscache overlay lz4hc lz4hc_compress zram rc_cec at2dec snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer sun4i_lradc_keys snd sun4i_ts sounm_hdmi sun4i_ss cec sun4i_drm sun8i_tcon_top sun4i_frontend sun4i_tcon uio_pdrv_genirq l libcomposite bonding ip_tables x_tables pwrseq_emmc [32673.130283] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.10-sunxi #5.65 [32673.137406] Hardware name: Allwinner sun7i (A20) Family [32673.142909] PC is at resched_curr+0x26/0x48 [32673.147313] LR is at check_preempt_curr+0x7f/0x84 [32673.152256] pc : [<c0139d12>] lr : [<c013a7cf>] psr: 000f01b3 [32673.158835] sp : c0d01d08 ip : ef6c87b0 fp : 2ea10000 [32673.164323] r10: ef6c8700 r9 : 00000000 r8 : ef6c8700 [32673.169813] r7 : c0d01d08 r6 : c0901ea0 r5 : c0d08a80 r4 : 00000000 [32673.176665] r3 : c0d00000 r2 : 00000000 r1 : c0d00000 r0 : 00000001 [32673.183519] Flags: nzcv IRQs off FIQs on Mode SVC_32 ISA Thumb Segment none [32673.191280] Control: 50c5387d Table: 6c8ec06a DAC: 00000051 [32673.197315] Process swapper/0 (pid: 0, stack limit = 0x385bb5af) [32673.203623] Stack: (0xc0d01d08 to 0xc0d02000) [32673.208212] 1d00: c0901f00 c0901f00 c0d01d18 c013a7cf ef6c8700 ea0 [32673.216802] 1d20: c0d01d74 c0d01d30 ea0d4bf8 c013a7ed ea0d4780 c012f663 80000000 ea0 [32673.225390] 1d40: c0d04f48 c0cb8700 c0d01d60 ea0d4bf8 00000000 ef6c8700 2ea10000 c01 [32673.233978] 1d60: c0901f00 b8023295 c0cb8700 600f0193 ea0d4800 ef6c8780 00000000 b80 [32673.242566] 1d80: ef6c8700 e5f55c10 00000000 00000000 c014fd75 ee7c5868 c0d01de8 000 [32673.251144] 1da0: 00000000 c014fd83 ee7c585c c014f7e7 00000004 00000001 2ea22000 ee7 [32673.259732] 1dc0: 00000001 00000003 00000000 c0d01de8 00000000 c0d04f48 600f0193 c01 [32673.268319] 1de0: 00000000 c0d01de8 00000000 00000000 00000000 c0d01df4 c0d01df4 b80 [32673.276907] 1e00: 00000400 ee7c5810 00000000 c0af4644 c0b1b080 0028f5be ee7c5870 600 [32673.285495] 1e20: ffffe000 c014f8ff 00000000 c073907f ee7c5810 c073909f 00000004 c01 [32673.294083] 1e40: ee01cfc0 ef100964 ef100900 00000000 00000035 ef03b800 c0d01ea0 c01 [32673.302671] 1e60: ef6c6450 c0623c2b 00001db7 c0d04f70 ef100900 c0de1ef8 00000000 c0d [32673.311251] 1e80: ef100964 ef100900 00000000 00000001 ef03b800 c0cb7870 00000000 c01 [32673.319839] 1ea0: 00000000 b8023295 ef100900 ef100964 2ea10000 c015f495 ef100900 c0d [32673.328427] 1ec0: 2ea10000 c0161cff c0cb8278 00000000 00000035 c015e8ed 0000008d c01 [32673.337015] 1ee0: c0d01f18 c0d05798 f080200c f0802000 c0d01f18 f0803000 c0d00000 c05 [32673.345603] 1f00: c0107a3c 400f0033 ffffffff c0d01f4c 00000000 c0101a65 00000000 0ea [32673.354192] 1f20: ef6c3438 c0116721 ffffe000 c0d04f70 c0d04fb8 00000001 00000000 c0d [32673.362772] 1f40: c0cb7870 00000000 ffffffff c0d01f68 c0107a3b c0107a3c 400f0033 fff [32673.371360] 1f60: 00000051 00000000 00000000 c013ea9b c0de1893 ffffffff c013ed1d b80 [32673.410865] 1f80: 60000033 000000c5 00000001 ffffffff c0d04f48 c0d04f40 c0df8a00 ef6 [32673.450651] 1fa0: c0c5da34 c013ed1d 00000001 c0c00bbd ffffffff ffffffff 00000000 c0c [32673.490033] 1fc0: 00000000 c0c5da34 b806219f 00000000 00000000 c0c00328 00000051 10c [32673.529069] 1fe0: 100010bb 49a8f000 410fc074 50c5387d 00000000 00000000 00000000 000 [32673.567780] [<c0139d12>] (resched_curr) from [<c013a7cf>] (check_preempt_curr+0x7f/0 [32673.606194] [<c013a7cf>] (check_preempt_curr) from [<c013a7ed>] (ttwu_do_wakeup+0x19 [32673.644826] [<c013a7ed>] (ttwu_do_wakeup) from [<c013b2ff>] (try_to_wake_up+0x15b/0x [32673.683009] [<c013b2ff>] (try_to_wake_up) from [<c014fd83>] (autoremove_wake_functio [32673.721302] [<c014fd83>] (autoremove_wake_function) from [<c014f7e7>] (__wake_up_com [32673.759336] [<c014f7e7>] (__wake_up_common) from [<c014f8c7>] (__wake_up_common_lock [32673.796627] [<c014f8c7>] (__wake_up_common_lock) from [<c014f8ff>] (__wake_up+0x13/0 [32673.832721] [<c014f8ff>] (__wake_up) from [<c073909f>] (mv64xxx_i2c_intr+0x2b7/0x3ec [32673.868190] [<c073909f>] (mv64xxx_i2c_intr) from [<c015f2d7>] (__handle_irq_event_pe [32673.904795] [<c015f2d7>] (__handle_irq_event_percpu) from [<c015f42d>] (handle_irq_e [32673.941488] [<c015f42d>] (handle_irq_event_percpu) from [<c015f495>] (handle_irq_eve [32673.976927] [<c015f495>] (handle_irq_event) from [<c0161cff>] (handle_fasteoi_irq+0x [32674.011371] [<c0161cff>] (handle_fasteoi_irq) from [<c015e8ed>] (generic_handle_irq+ [32674.045560] [<c015e8ed>] (generic_handle_irq) from [<c015ed8d>] (__handle_domain_irq [32674.079597] [<c015ed8d>] (__handle_domain_irq) from [<c05cac95>] (gic_handle_irq+0x3 [32674.112894] [<c05cac95>] (gic_handle_irq) from [<c0101a65>] (__irq_svc+0x65/0x94) [32674.145236] Exception stack(0xc0d01f18 to 0xc0d01f60) [32674.175010] 1f00: 00000000 0ea [32674.207967] 1f20: ef6c3438 c0116721 ffffe000 c0d04f70 c0d04fb8 00000001 00000000 c0d [32674.240863] 1f40: c0cb7870 00000000 ffffffff c0d01f68 c0107a3b c0107a3c 400f0033 fff [32674.273876] [<c0101a65>] (__irq_svc) from [<c0107a3c>] (arch_cpu_idle+0x28/0x2c) [32674.306067] [<c0107a3c>] (arch_cpu_idle) from [<c013ea9b>] (do_idle+0x14b/0x1d8) [32674.338165] [<c013ea9b>] (do_idle) from [<c013ed1d>] (cpu_startup_entry+0x19/0x1c) [32674.370035] [<c013ed1d>] (cpu_startup_entry) from [<c0c00bbd>] (start_kernel+0x3a7/0 [32674.402141] Code: 53ff 2001 f023 031f (691b) 42a3 [32674.430709] ---[ end trace 349b2715ffd50e9f ]--- [32674.458898] Kernel panic - not syncing: Fatal exception in interrupt [32675.648500] SMP: failed to stop secondary CPUs [32675.675135] Rebooting in 10 seconds.. [32686.861416] SMP: failed to stop secondary CPUs thanks and regards, Lazar
  8. I did the following upgrades this morning libcurl3:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libgd3:armhf (2.2.4-2+deb9u3, 2.2.4-2+deb9u4), armbian-config:armhf (5.72, 5.74), linux-headers-next-sunxi:armhf (5.70, 5.73), linux-image-next-sunxi:armhf (5.70, 5.73), curl:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), libcurl3-gnutls:armhf (7.52.1-5+deb9u8, 7.52.1-5+deb9u9), linux-dtb-next-sunxi:armhf (5.70, 5.73), base-files:armhf (9.9+deb9u6, 9.9+deb9u7) and found my I2C bus not working anymore. I did a scan on the 4 buses (Olinuxino Micro A20) and found a device on i2c-1 instead of i2c-0, changed my settings and all worked again, so I guess one of the updates must have changed the labeling of the busses? Is this by accident or on purpuse?
  9. Hello, I am having strange problem with Olimexino A20 Micro, Ambian 5.38, 4.14.14. After every 2-3 days standby with minor cpu usage I am getting an FS error. I have tried Armbian Ubuntu/Debian and different sd cards but this doesn't change anything. I think with previous kernel there wasn't such an issue. I've connected it to the serial port and I see: login: [381301.434449] EXT4-fs error (device mmcblk0p1): ext4_journal_check_setected aborted journal [381301.444715] EXT4-fs (mmcblk0p1): Remounting filesystem read-only [381340.727458] EXT4-fs error (device mmcblk0p1): ext4_find_entry:143621620: comm sh: reading directory lblock 0 [381494.351427] EXT4-fs error (device mmcblk0p1): ext4_find_entry:143643740: comm /usr/share/webm: reading directory lblock 0 [381494.367402] EXT4-fs error (device mmcblk0p1): ext4_find_entry:143643740: comm /usr/share/webm: reading directory lblock 0 [381804.544643] EXT4-fs error (device mmcblk0p1): ext4_find_entry:143643740: comm /usr/share/webm: reading directory lblock 0 My installation is Welcome to ARMBIAN 5.38 stable Ubuntu 16.04.4 LTS 4.14.18-sunxi System load: 0.43 0.41 0.40 Up time: 1 day Memory usage: 53 % of 997MB Swap usage: 8 % of 498Mb IP: CPU temp: 40°C HDD temp: 32°C Usage of /: 8% of 29G storage/: 33% of 917G Batter [ General system configuration (beta): armbian-config ] Last login: Wed Jul 18 17:43:03 2018 from Does anyone have same issue or any idea how to fix that? Regards, Lazar
  10. Hello I am new in this forum, I need to configure A20-OLinuXino-MICRO 4G Nand board so that it has native vga output. As I can do, please, please, that any member of this forum can guide me.
  11. I just installed a fresh armbian 5.38 (mainline kernel) image to an SD Card for my A20-OLinuXino-MICRO board. After booting I used armbian-config to enable the spi-spidev. I then edited the armbianEnv.txt directly to add param_spidev_spi_bus=0. This gives me a single spidev0.0 under dev. Changing the parameter to param_spidev_spi_bus=2 (or 1) I can get the other busses. But only a single bus at a time. I spent I few hours googling, but I cannot seem to find any documentation on how to enable more than one userspace spi dev. Could someone explain to me how to enable all spi devices at once? Writing a custom overlays myself is a little beyond me at the moment.
  12. Hello I have an issue with my HDMI display. Some of the desktop is out of screen. This is about 3% or 15px all around the screen. Changing resolution from 1080p down to 720p and down to 800x600 doesn't fix the borders. Armbian-config allows me to edit the booting environment. Atleast these lines won't work: disable_overscan=0 .... this can also be 1 with no effect overscan_x=-30 overscan_y=-30 .... these can also be positive with no effect also overscan_top, overscan_bottom, overscan_left and overscan_right don't work Only line that changes something is the one with resolution: disp_mode=800x600p60 I don't have zoom on this display or I have lost the correct remote so I can't access zoom. Atleast 3 remotes with zoom buttons won't work. So I need to have a software fix. My kernel is 3.4.113-sun7i running on A20 Olimex Micro. It is installed on micro SD This distro on this board worked just fine with 2 of my reqular PC displays with HDMI connectors. I just want to change to this 12V mobile TV display so I can use it on a boat. Edit1: I've also tried xrandr with no luck... somehow it doesn't accept the screen name regardless of what I type Any help is appreciated because right now I'm out of ideas.
  13. I've just downloaded the Debian-server mainline image for my Olinuxino A20 Micro (Armbian_5.38 etc) and tried, without success, to change the video output from the default HDMI to the VGA one. Following the documentation (https://docs.armbian.com/Hardware_Allwinner/) I modified the boot.cmd file adding the lines: setenv video-mode sunxi:monitor=vga,hpd=0,edid=0 saveenv and recompiling it but the video continues to be enabled on the HDMI output, also after 2 (and more) restart. I noticed that in the boot splash screen a "Err: VGA" is reported. It's not too clear from the documentation if this setting can be applied also modifying the armbianEnv.txt file or if editing and recompiling the boot.cmd file is the right way, anyway my question is: what should in order to enable the VGA output? Thank you in advance
  14. Hello ! I am use A20-OLinuXino-MICRO-e4GB Debian server image with mainline kernel work fine with eMMC, but I need eMMC support in Ubuntu desktop with legacy kernel. How I can do it ? Sorry for bad English :-) I hope, you understood me :-). Thank !
  15. Hello All, Trying to get sound working on my A20 micro. After switching to the Mainline kernel, the sun4i_codec loads and everything seems to be there. But alsamixer, aplay, etc all say that there's no such device. Running as root does not help so this is not a permissions issue. mute@micro:~$ uname -a Linux micro 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux mute@micro:~$ dmesg |grep sun4i-codec [ 10.491588] sun4i-codec 1c22c00.codec: Codec <-> 1c22c00.codec mapping ok mute@micro:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun4icodec [sun4i-codec], device 0: CDC PCM Codec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 mute@micro:~$ alsamixer cannot open mixer: No such device mute@micro:~$ lsmod |grep snd snd_soc_core 118784 1 sun4i_codec snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 65536 2 snd_pcm_dmaengine,snd_soc_core snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd mute@micro:~$ speaker-test speaker-test 1.0.28 Playback device is default Stream parameters are 48000Hz, S16_LE, 1 channels Using 16 octaves of pink noise ALSA lib pcm_hw.c:1667:(_snd_pcm_hw_open) Invalid value for card Playback open error: -19,No such device I would be most grateful for any suggestions. -B
  16. Hello, I am using the Olimex OLinuxino and I find a constant noise at about 866.725MHz or thereabout in every board. While low, at -100dBm, when using it with IoT radios this is the band in India and it is quite a pain in applications requiring high sensitivity. This particular board had it pretty nasty at -86dB. I have tried with changing the DDR frequency as well as the CPU clock, however this nuisance refuses to go away. What can be done to get rid of this noise ? I have tried multiple boards -- Olinuxino (multiple), Marsboard, but each has some noise in exactly same band near 866MHz. Please advise.
  17. Is it possible to boot from harddisk (ssd) without the need of the sd-card. I am using an A20-OLinuXino-MICRO from OLIMEX. After flashing sd wih image and setting up boot from sata or usb by the use of armbian-config sd card is still needed. Would the A20 recognize u-boot (bootloader) on diffrent device than sd-card?
  18. I flashed the Armbian 5.35 4.13.16 image and at boot time I sometimes got faults and the OS doesnt boot. The clean install also produced sometimes the error or warning but I started to customize the system with enabling overlays and now its cant boot. I restored the initial state of the uEnv through my computer but the bug is still running. I copied the messages to pastebin: http://pastebin.com/2NUGVnqt I dont know where can I start the debugging and how to find what is wrong. I have C skills but I never debug the kernel so its a good time to start, but first it is a serious bug because the system is useless.
  19. Hi, i have a Olimex Olinuxino-micro-emmc and the armbian image 5.31 and 5.25 booting fine but NO network is comming up. The link led's are on but no once Packet will be transmitted. The same board with my own u-boot/kernel version has no problems with network device. is it a bug or a feature? Best regards Mike
  20. Hi, i'm new on this forum. I have compiled u-boot 2017.3 and Mainline 4.14 for my own for Olimex-olinuxino-micro-emmc - and it is runnig ;-) But when i reboot the board, u-boot hangs with: U-Boot SPL 2017.03+ (Oct 03 2017 - 18:24:31) DR Only reseting or repowering helps. any ideas?
  21. Hello there, I just flashed latest armbian (downloaded yesterday) on my A20 Olinuxino Micro. Version was with legacy kernel as my use case involves multimedia. SD card is Samsung Evo 128GB. Once I attach HDMI display, I can see armbian logo and something happening (booting kernel etc) just for a few seconds, then screen flashes with colors and I don't get anymore signal. I tried with two monitors with the same reult. Later today I will try using cable-f attached to pins to see wether something is happening under the hood (I expect yes). In the meantime can someone confirm this issue? What should I try in order to fix this? Thanks in advance for any help on this. Antonio
  22. Hi All, I'm using the latest Debian mainline kernel image -> Armbian_5.31_Micro_Debian_jessie_next_4.11.5. I can't get the USB OTG port to work as host only. I was using the legacy kernel before and below setup was working for me -> [usbc0] usb_used = 1 usb_port_type = 1 usb_detect_type = 0 usb_drv_vbus_gpio = port:PB09<1><0><default><0> usb_restrict_gpio = usb_host_init_state = 1 usb_restric_flag = 0 I read on another post that usb0 mode is host on armbian images by default. I also read about needing to load the g_serial module for Banana pi, but I don't think it's required here. Do I need to make any changes to the dts? Thank you for your help.
  23. I want to use an ADAU1979 with an olimex A20-Micro. Needs to show up as a device in ALSA, alongside the in- built CODEC - As far as I can see, this driver is in mainline kernel but I have no idea how to configure the kernel build to include it. Obviously we need to tell the system where its i2s/SPI interface is connected etc. Unsure which kernel version (legacy or mainline) to begin with. We do need a desktop environment and the olimex 10"/7" LCD to work also... I am starting this from a position not having built a kernel or kernel modules before so If this idea is a non-starter, someone please tell me so. Thanks.
  24. I got a new board revision of the Olimex A20-OLInuXino-MICRO Board (Rev. J). It works with the by Olimex provided Jessie image but not with Armbian_5.25_Micro_Debian_jessie_next_4.9.7. I get no IP address by DHCP because the ethernet is not working. The reason could be an new ethernet chipset they introduced with this revision. New: Microchip's LAN8710AI-EZK(QFN-32). Before: Realtek RTL8201CP(LQFP-48) They publish a patch on: https://github.com/OLIMEX/OLINUXINO/blob/master/SOFTWARE/A20/A20-build-3.4.103-release-5/a20-phy_1000_100-dram.patch
  25. Since a few weeks Olimex delivers their 4GB Variant of the Olinuxo A20 Micro with standard eMMC (See this revision https://github.com/OLIMEX/OLINUXINO/blob/master/HARDWARE/A20-OLinuXino-MICRO/A20-OLINUXINO-MICRO-EMMC_Rev_J.pdf) Onfortunality the Armbian Version for this board does not support eMMC (Although it is not recognized). How can I enable this support? Kind regards, Pieter
  • Create New...