Zaxter

Members
  • Content Count

    9
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Calendar

Everything posted by Zaxter

  1. I was able to solve the problem. It was related to UART settings in the Fex file. Somehow, I hadn't set the pull-up on UART6 & UART7. -> [uart_para6] uart_used = 1 uart_port = 6 uart_type = 2 uart_tx = port:PI12<3><default><default><default> uart_rx = port:PI13<3><default><default><default> # ^ # | # Here It should've been -> [uart_para6] uart_used = 1 uart_port = 6 uart_type = 2 uart_tx = port:PI12<3><1><default><default> uart_rx = port:PI13<3><1><default><default> I guess I will be moving to the mainline kernel in the future.
  2. Thanks for pointing me in the right direction @zador.blood.stained. Here are the crash logs from serial console: root@micro:~# cat /dev/ttyS2 <4>i2c-0, xfer timeout [ 63.123577] i2c-0, xfer timeout <3>axp_mfd 0-0034: failed reading at 0x23 [ 63.130520] axp_mfd 0-0034: failed reading at 0x23 <3>[cpu_freq] ERR:try to set voltage failed! [ 63.139404] [cpu_freq] ERR:try to set voltage failed! And here's the dmesg output for registered uarts: root@micro:~# dmesg | grep uart [ 0.996902] [uart]: used uart info.: 0xc9 [ 1.001620] [uart]: serial probe 0 irq 33 mapbase 0x01c28000 [ 1.027944] sunxi-uart.0: ttyS0 at MMIO 0x1c28000 (irq = 33) is a U6_16550A [ 1.889704] [uart]: serial probe 3 irq 36 mapbase 0x01c28c00 [ 1.921599] sunxi-uart.3: ttyS1 at MMIO 0x1c28c00 (irq = 36) is a U6_16550A [ 1.933439] [uart]: serial probe 6 irq 51 mapbase 0x01c29800 [ 1.965318] sunxi-uart.6: ttyS2 at MMIO 0x1c29800 (irq = 51) is a U6_16550A [ 1.977174] [uart]: serial probe 7 irq 52 mapbase 0x01c29c00 [ 2.009053] sunxi-uart.7: ttyS3 at MMIO 0x1c29c00 (irq = 52) is a U6_16550A Have you seen something like this before?
  3. I'm not sure why, but this is the behaviour I'm currently seeing. It may have to do with the fact that I've set uart_used = 0 for all UARTs but 0,3,6 & 7. So, although I do get ttyS0 -> ttyS7, UARTs 0,3,6 & 7 are configured as ttyS0 to ttyS3 & I can't access >ttyS3. $ cat /dev/ttyS7 cat: /dev/ttyS7: Input/output error
  4. I'm running Armbian_5.20_Micro_Debian_jessie_3.4.112 on an Olimex A20 micro board. I find that opening serial port device `/dev/ttyS2` causes the system to crash. The board heartbeat LED either stops or blinks rapidly. The board itself is not pingable. I can reproduce this issue with a simple from the shell using: cat /dev/ttyS2 or from c code using: fd = open("/dev/ttyS2", O_RDWR | O_NOCTTY | O_NDELAY); `/dev/ttyS2` is linked to UART6. In the fex file, I have configured it like so: [uart_para6] uart_used = 1 uart_port = 6 uart_type = 2 uart_tx = port:PI12<3><default><default><default> uart_rx = port:PI13<3><default><default><default> Note that the UART6 is on MUX3 as it should be according to sunxi's pio documentation for A20. Any ideas?
  5. Thanks for your reply Igor. I just wanted to mention that I'm able to boot from NAND without any problems using your recent `Armbian_5.20_Micro_Debian_jessie_3.4.112.img` image on the same board. Everything including ethernet works perfectly fine even on subsequent attempts. This leads me to believe that my problem here (i.e. proc not being mounted on boot) is not related to the GMAC.
  6. Hi All, I'm using a rather old Armbian (wheezy) image on an Olimex Micro. I've installed a lot of apps on it, so I don't want to be moving to a newer image. I'm trying to copy my SD card image to NAND using the `nand-sata-install.sh` script that came with the image. All goes well. The script partitions the NAND, reboots, installs all files and shuts down. When I remove the SD card and power on, the board boots and everything is still alright. Now, on subsequent poweroffs or reboots, the board does boot, but I doesn't connect to ethernet. Boot logs from debug UART show that `proc` isn't mounted. Error: /proc must be mounted What could be the reasons for this?
  7. There's no /proc/nand either. I have tried a lot of different images here and I have the same problem. I'll check to see if there's something wrong on the hardware side. Thank you again for your help @igor.
  8. Thanks for your replies @wildcat and @igor. I think my fex config is alright. I use the same fex with another board and the nand device shows up straight away. I also don't get why Livesuite fails to write to the nand. Quick question: Would the nand device (i.e. /dev/nand) show up even if it was never partitioned / pre-written with an Android NAND image?
  9. Hi All, I'm using Armbian_5.10_Micro_Debian_jessie_3.4.112 on a custom A20 board with NAND based off the Olimex A20 Micro. I don't see /dev/nand on it. $ zgrep NAND /proc/config.gz CONFIG_SUNXI_NAND_PARTITION=y CONFIG_SUNXI_NAND=y # CONFIG_SUNXI_NAND_COMPAT_DEV is not set # CONFIG_SUNXI_NAND_TEST is not set I even tried to Livesuite an Android NAND image, but it also failed. I'm pasting the logs below. What does it generally mean to have a missing /dev/nand? Thanks.