martinayotte

Members
  • Content count

    695
  • Joined

  • Last visited

1 Follower

About martinayotte

  • Rank
    Embedded member

Recent Profile Visitors

474 profile views
  1. I've got the RTL8723bs working using a temporary build of 4.12 ...
  2. No, I don't have such behaviour. My SSH session are pretty normal in STA mode.
  3. preview

    Apologize ! I didn't knew that since all my boards are AllWinner.
  4. preview

    It could be defined, but not enabled by default ... Another to verify DT is using "cat status", for example here checking uart1 and uart2 on some AllWinner boards : cat /proc/device-tree/soc/serial@01c28000/status okay cat /proc/device-tree/soc/serial@01c28400/status disabled How to enable uart2 uising overlays ? simply edit /boot/armbianEnv.txt and add "overlays=uart2" In the meantime, yes, using USB-TTL Serial is a good workaround ...
  5. Nice picture ! Those parrots are even following the electronic color coding, although there are some missing ones : black/brown at left and gray/white at right ...
  6. preview

    Like many other boards, even if you have many /dev/ttyS*, it doesn't mean the actual UARTs are enabled in the DeviceTree. You should probably look in the DTS (or decompile DTB into DTS) to figured out. When a UART is detected at boot time, you will see it in "dmesg" which will show on which /dev/tttyS* it will be attached. BTW, if not enabled, UARTs can also be enabled using overlays ...
  7. UART1 is dedicated to on-board Bluetooth of the AP6212, so not available on headers. UART2 is working, like I've experiment earlier. UART3 could be also enabled, but you will loose the SPI1 on header, the pins should be 23 and 24.
  8. Yes, Zador is right ! We shouldn't "trash" the WIPs, but simply hide them and make them visible with EXPERT=yes. Otherwise, it will be a pain even for experts ...
  9. Why are you showing us a 40 pins header while OPiZeroPlus2 has only a 26 pins one ? As I said earlier, simply do a loopback test ! It is what I've just did : - connect a jumper between pins 8 and 10 of the 26 pins OPiZeroPlus2 header. - add "overlays=uart2" (I don't know why you've added ttyS1 in overlays, such overlay doesn't exist !) - reboot - then "picocom -b 115200 /dev/ttyS2" and type any thing, it will be echoed ...
  10. Then, it should work ! Probably your wiring ... Are you sure you need rtscts ? maybe the problem is there ... You can try a loopback wire without rtscts, then use picocom or other terminal to test the echo.
  11. Did you plug a USB-TTL Serial adaptor to do debugging ? You should see the login prompt without any problem. That said, this image is WIP, WiFi still glitchy, and EMAC not yet implemented. But that doesn't prevent Armbian for booting, so in the meantime, I'm using MT7601 USB dongle to get networking ...
  12. BTW, I've built a Armbian_5.27_Bananapim2ultra_Debian_jessie_dev_4.11.0-next-20170427.img image 2 days ago, and it is booting fine. The only thing is that the WiFi AP6212 isn't in good shape yet : wlan0 could be activated, but the issue is that it doesn't receive response from DHCP request. I think it is due to the fact that WL-WAKE is connected to AXP GPIO instead of PLx, and therefore the NMI is managed well.
  13. Your display is not with a SPI interface, all transfers are done with parallel GPIOs. So, don't expect been able to run it using frame buffer. You can use GPIO library to drive it, but you are on your own displaying something from your own application.
  14. I've not tried the AP mode ...
  15. Did you tried full image ? What errors/problems do you have ?