martinayotte
-
Posts
3892 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by martinayotte
-
-
-
-
We should probably add that patch to Armbian until Mainline is merging it ...
-
The screenshot you've provided confirmed that it is Legacy, so no need to change any DTS.
Unfortunately, I can't help on Legacy ... Maybe someone else can help ...
-
Then, you will need to tweak either DTS on Mainline or FEX on Legacy to enable those UARTs.
-
Strangely, I've got the WiFi working on M2+ once about 3 weeks ago (remember I've posted that they ship me sample without any antenna) , but since then it is not even able to scan APs. I think the AP6212 on my board simply become dead on radio side, although the wlan0 still appears with the latest firmware.
-
For the Arduino code, yes, this could help, but it is not handled as a kernel driver, so don't expect it to bee seen as /dev/ttyXXX.
For the MAX14830, yes, mainline kernel is already supporting it, so it should be straight-forward ...
-
-
It should, the wlan0 is appearing, but for some unknown reason, it could not get response from DHCP request.
I'm also having same kind of issue on BPiM2Ultra.
I didn't get chance recently to pursue the investigation, but I hope I will soon.
EDIT : After comparing results between my M2+ and my M2U, the latest is able to scan APs but not the M2+. So, I presume my M2+ is now defective.
-
Why are you not sticking with Armbian ?
-
Then, maybe recoverable : copy /lib/firmware/ap6212/fw_bcm43438a1.bin over /lib/firmware/brcm/brcmfmac43430-sdio.bin
And reboot ...
-
Of course, but this board isn't supported by kernels, so your app will have to take care of it.
If you wish that the kernel provide direct driver connection into /dev/ttyXXX, maybe you should use boards that are using SC16IS752.
-
I don't see any relation between wlan0 and eMMC, especially that you mentioned that booting again from SD doesn't make it reappear ...
Did you check for any traces in "dmesg" ?
-
I've migrated the patches from sunxi-next into sunxi-dev !
https://github.com/armbian/build/commit/20240e9669055030076e69452cf6a1ccb368cc2e
Unfortunately, during my migration of my 3x Olimex-A20-Micro boards, I've faced strange hangs during Armbian Filesystem Resize service.
One of the boards, I wait 5 mins, but service was still hanging/looping. I've have then press reset button, reboot, automatic fsck, then resize Ok !
So, can other A20-Micro owner can confirm ? ...
-
I've got the RTL8723bs working using a temporary build of 4.12 ...
-
11 hours ago, t-bob said:
I have noticed that sometimes the connection seems to 'stutter' ... you type away and then get all the characters in a surge ? have you noticed such a thing ?
No, I don't have such behaviour. My SSH session are pretty normal in STA mode.
-
Apologize ! I didn't knew that since all my boards are AllWinner.
-
Quote
DTS is the Device Tree given by DTB (from the bootloader), which contains all the devices that "should turn on", practically speaking.
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 disabledHow 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 ...
-
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 ...
-
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 ...
-
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.
-
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 ...
-
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 ...
-
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.
hostapd on orange pi light realtek driver
in Allwinner sunxi
Posted
There is no relation between your network DHCP and the HOSTAP DHCP, you need to run a DHCP server on your OrangePi to serve its clients.