- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
A20 / Re: Working Linux driver for U...
Last post by sasha2002 - Today at 11:15:48 AMCode Select
root@a20-olinuxino:~# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 350b:f179 ZTOP ztop CDROM
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@a20-olinuxino:~# eject /dev/sr0
lsusb
dmesg | grep -Ei '350b|9612|f179|ztop|zt9612|firmware|wlan|wifi|usb' | tail -120
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[ 1.828739] usbcore: registered new interface driver usbhid
[ 1.828749] usbhid: USB HID core driver
[ 2.032252] ehci-platform 1c14000.usb: EHCI Host Controller
[ 2.032504] ehci-platform 1c14000.usb: new USB bus registered, assigned bus number 1
[ 2.033061] ehci-platform 1c14000.usb: irq 42, io mem 0x01c14000
[ 2.048376] ehci-platform 1c14000.usb: USB 2.0 started, EHCI 1.00
[ 2.048798] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.048814] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.048824] usb usb1: Product: EHCI Host Controller
[ 2.048832] usb usb1: Manufacturer: Linux 5.10.180-olimex ehci_hcd
[ 2.048840] usb usb1: SerialNumber: 1c14000.usb
[ 2.049933] hub 1-0:1.0: USB hub found
[ 2.051596] ehci-platform 1c1c000.usb: EHCI Host Controller
[ 2.051641] ehci-platform 1c1c000.usb: new USB bus registered, assigned bus number 2
[ 2.052131] ehci-platform 1c1c000.usb: irq 47, io mem 0x01c1c000
[ 2.064494] ehci-platform 1c1c000.usb: USB 2.0 started, EHCI 1.00
[ 2.065002] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.065017] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.065027] usb usb2: Product: EHCI Host Controller
[ 2.065035] usb usb2: Manufacturer: Linux 5.10.180-olimex ehci_hcd
[ 2.065043] usb usb2: SerialNumber: 1c1c000.usb
[ 2.066353] hub 2-0:1.0: USB hub found
[ 2.068075] ohci-platform 1c14400.usb: Generic Platform OHCI controller
[ 2.068118] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3
[ 2.068768] ohci-platform 1c14400.usb: irq 43, io mem 0x01c14400
[ 2.132724] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.132749] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.132759] usb usb3: Product: Generic Platform OHCI controller
[ 2.132767] usb usb3: Manufacturer: Linux 5.10.180-olimex ohci_hcd
[ 2.132776] usb usb3: SerialNumber: 1c14400.usb
[ 2.133686] hub 3-0:1.0: USB hub found
[ 2.135445] ohci-platform 1c1c400.usb: Generic Platform OHCI controller
[ 2.135491] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4
[ 2.136113] ohci-platform 1c1c400.usb: irq 48, io mem 0x01c1c400
[ 2.196737] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 5.10
[ 2.196755] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.196765] usb usb4: Product: Generic Platform OHCI controller
[ 2.196774] usb usb4: Manufacturer: Linux 5.10.180-olimex ohci_hcd
[ 2.196781] usb usb4: SerialNumber: 1c1c400.usb
[ 2.197750] hub 4-0:1.0: USB hub found
[ 2.199591] usb_phy_generic usb_phy_generic.0.auto: supply vcc not found, using dummy regulator
[ 2.199874] usb_phy_generic usb_phy_generic.0.auto: dummy supplies not allowed for exclusive requests
[ 2.201177] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[ 2.201225] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5
[ 2.201767] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10
[ 2.201782] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 2.201791] usb usb5: Product: MUSB HDRC host driver
[ 2.201799] usb usb5: Manufacturer: Linux 5.10.180-olimex musb-hcd
[ 2.201807] usb usb5: SerialNumber: musb-hdrc.1.auto
[ 2.202741] hub 5-0:1.0: USB hub found
[ 2.388525] usb 2-1: new high-speed USB device number 2 using ehci-platform
[ 2.546304] usb 2-1: New USB device found, idVendor=350b, idProduct=f179, bcdDevice= 2.00
[ 2.546329] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.546341] usb 2-1: Product: ztop CDROM
[ 2.546350] usb 2-1: Manufacturer: ZTOP
[ 2.548251] usb-storage 2-1:1.0: USB Mass Storage device detected
[ 2.549888] scsi host1: usb-storage 2-1:1.0
[ 2.564570] usb 3-1: new low-speed USB device number 2 using ohci-platform
[ 2.793204] usb 3-1: New USB device found, idVendor=046d, idProduct=c31c, bcdDevice=64.00
[ 2.793230] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.793241] usb 3-1: Product: USB Keyboard
[ 2.793250] usb 3-1: Manufacturer: Logitech
[ 2.807901] input: Logitech USB Keyboard as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.0/0003:046D:C31C.0001/input/input1
[ 2.865050] hid-generic 0003:046D:C31C.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-1c14400.usb-1/input0
[ 2.878423] input: Logitech USB Keyboard Consumer Control as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.1/0003:046D:C31C.0002/input/input2
[ 2.937519] input: Logitech USB Keyboard System Control as /devices/platform/soc/1c14400.usb/usb3/3-1/3-1:1.1/0003:046D:C31C.0002/input/input3
[ 2.938166] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Device [Logitech USB Keyboard] on usb-1c14400.usb-1/input1
[ 3.562006] scsi 1:0:0:0: CD-ROM S9612USB CDROM AUTORUN V1.0 PQ: 0 ANSI: 0 CCS
[ 3.704440] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.016501] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.316520] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.616554] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 4.912531] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.212368] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.512348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 5.812345] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 6.307796] usbcore: registered new interface driver uas
[ 6.520386] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 6.820356] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.120347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.420343] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 7.712348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.012347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.312348] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 8.612345] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.120384] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.420352] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 9.720344] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.020347] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.312351] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.612346] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 10.912344] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 11.212350] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 14.961210] systemd[1]: Reached target paths.target - Path Units.
[ 20.084539] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 20.480511] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 20.792520] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.100487] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.400510] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 21.692534] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.008524] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.308484] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.616537] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 22.932555] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.232540] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.532594] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 23.832491] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.152041] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.472461] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 24.776525] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 25.080624] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 25.948531] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.248479] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.548463] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 26.848439] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.144401] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.448399] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 27.752372] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 28.060371] usb 2-1: reset high-speed USB device number 2 using ehci-platform
[ 921.293484] usb 2-1: USB disconnect, device number 2
root@a20-olinuxino:~# lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 350b:9612 ZTOP 802.11ax 2x2 WLAN Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@a20-olinuxino:~#
#2
A64 / Re: A64-OlinuXino-2Ge16G-IND E...
Last post by LubOlimex - August 31, 2026, 11:39:25 AMThank you for this. I want to post update in this topic since it had been recently brought up by another customer.
The reset circuit of the Ethernet can be handled passively or via GPIO pin connected to the main chip.
There are advantages and disadvantages of each option. In the hardware design of our A64 boards we have chosen the second option - connect the Ethernet reset to a GPIO of the A64 chip (in our case specifically pin "PD24") - this allows to reset just the Ethernet, by toggling this GPIO PD24, if a problem with the Ethernet appears. It is very convenient for systems where reliability is important and where the whole board shouldn't be power cycled when Ethernet hangs. Now - the down-side is that your software should take care of the GPIO pin that is routed to the reset of the Ethernet (e.g. during power-up either keep it in reset long enough, or maybe even simpler, just run one time reset at some point during boot). This software work is now done in our Olimage Linux, it handles PD24 during power-up.
Of course, if you use custom Linux and you have Ethernet issues during power up or reset, you can add some software control for PD24 and fix it.
Alternatively, give up on the software method and go the hardware option we have provided. Simply unsolder R117 (1K) and solder it to R118 position. This will disconnect the Ethernet reset from PD24 GPIO, and connect it to the passive auto-reset circuit. This simplifies the design but disables the option to reset ONLY the Ethernet via GPIO (e.g. if the Ethernet hangs and it is not possible to recover you will need to reset the whole board).
The reset circuit of the Ethernet can be handled passively or via GPIO pin connected to the main chip.
There are advantages and disadvantages of each option. In the hardware design of our A64 boards we have chosen the second option - connect the Ethernet reset to a GPIO of the A64 chip (in our case specifically pin "PD24") - this allows to reset just the Ethernet, by toggling this GPIO PD24, if a problem with the Ethernet appears. It is very convenient for systems where reliability is important and where the whole board shouldn't be power cycled when Ethernet hangs. Now - the down-side is that your software should take care of the GPIO pin that is routed to the reset of the Ethernet (e.g. during power-up either keep it in reset long enough, or maybe even simpler, just run one time reset at some point during boot). This software work is now done in our Olimage Linux, it handles PD24 during power-up.
Of course, if you use custom Linux and you have Ethernet issues during power up or reset, you can add some software control for PD24 and fix it.
Alternatively, give up on the software method and go the hardware option we have provided. Simply unsolder R117 (1K) and solder it to R118 position. This will disconnect the Ethernet reset from PD24 GPIO, and connect it to the passive auto-reset circuit. This simplifies the design but disables the option to reset ONLY the Ethernet via GPIO (e.g. if the Ethernet hangs and it is not possible to recover you will need to reset the whole board).
#3
A20 / Re: Working Linux driver for U...
Last post by LubOlimex - August 26, 2026, 04:55:44 PMAh, it is probably with a different chipset. What does it list as before ejecting, e.g. unplug/plug?
lsusb
After ejecting is clear but still what does this return:
eject /dev/sr0
lsusb
dmesg | grep -Ei '350b|9612|f179|ztop|zt9612|firmware|wlan|wifi|usb' | tail -120
lsusb
After ejecting is clear but still what does this return:
eject /dev/sr0
lsusb
dmesg | grep -Ei '350b|9612|f179|ztop|zt9612|firmware|wlan|wifi|usb' | tail -120
#4
A64 / Re: Debian GNU/Linux 13 (Trixi...
Last post by Roman - August 23, 2026, 10:18:34 PMQuote from: Roman on June 06, 2026, 08:09:08 PMBut I would rather see the issue fixed in the upstream.
I was pointed to the documentation about the Ethernet PHY modes. It explains which mode to use depending on how the 2 ns RGMII delay is implemented.
Quote# One option is to make the clock traces on the PCB longer than the
# data traces. A sufficiently difference in length can provide the 2ns
# delay. If both the RX and TX delays are implemented in this manner,
# 'rgmii' should be used, so indicating the PCB adds the delays.
#
# If the PCB does not add these delays via extra long traces,
# 'rgmii-id' should be used. Here, 'id' refers to 'internal delay',
# where either the MAC or PHY adds the delay.
I tried calculating the legths of the tracks and counting resistrors in the PCB schematics and concluded that they are unlikely to bring any significant delays. I tried 'rgmii-id' and it worked without additional adjustments to both RX and TX delays in the device tree, so the driver configures the delays for that mode.
Assuming that the submitted upstream patch is accepted into Linux release 7.3, a kernel with that fix to the device tree may eventually become available in Debian backports.
#5
A20 / Re: LIME2-4GB dead or not?
Last post by LubOlimex - August 21, 2026, 08:41:09 AMYes, since SD card is good and you used Olimage base, and you prepared the SD card with Balena and there is still nothing on the HDMI monitor, it appears the board got damaged somehow. Now looking at your first post I see this part, which I missed initially somehow (silly me):
"Yesterday, I tried with another power supply adapter, with Output 12V / 1A / 12 W"
This damaged the board for sure since LIME2 is 5V only board. The board got damaged by overvoltage for sure, even if the initial problem was something else. Anything above 6V DC will burn the D3 diode at the power jack. My advice is:
Desolder D3 diode and test with 5V DC only supply to see if it works. Hopefully only the protection diode on the input got damage and the rest of the circuit is alright. If it works without D3 make sure to purchase such diode and replace the burned one (else the board will be without protection for future overvoltages). Again make sure NOT to use 12VDC power supply, 5V DC only!
About D3 - it is the big black component just under the powerjack and it is hard to desolder due to its size and placement. You need some basic soldering experience, since it is possible to desolder other components around it if you hold the solderin iron too long or if you don't insulate nearby soldering points with tin foil. It is usually sufficient to desolder one leg and carefully lift it. However, since the board doesn't work anyway trying this is better than just throwing it away!
It might be good idea to also check what happens over the terminal if you have USB-serial cable to attach to the three UART0 pins (near the Ethernet connector), this will help us see whether it boots at all and where the boot stops.
Another good idea for diagnostic is measuring with multimeter or voltage meter, for example at the GPIO headers if the is 5V DC when the board is powered, and track where the voltage disappears between the power jack and the main chip.
"Yesterday, I tried with another power supply adapter, with Output 12V / 1A / 12 W"
This damaged the board for sure since LIME2 is 5V only board. The board got damaged by overvoltage for sure, even if the initial problem was something else. Anything above 6V DC will burn the D3 diode at the power jack. My advice is:
Desolder D3 diode and test with 5V DC only supply to see if it works. Hopefully only the protection diode on the input got damage and the rest of the circuit is alright. If it works without D3 make sure to purchase such diode and replace the burned one (else the board will be without protection for future overvoltages). Again make sure NOT to use 12VDC power supply, 5V DC only!
About D3 - it is the big black component just under the powerjack and it is hard to desolder due to its size and placement. You need some basic soldering experience, since it is possible to desolder other components around it if you hold the solderin iron too long or if you don't insulate nearby soldering points with tin foil. It is usually sufficient to desolder one leg and carefully lift it. However, since the board doesn't work anyway trying this is better than just throwing it away!
It might be good idea to also check what happens over the terminal if you have USB-serial cable to attach to the three UART0 pins (near the Ethernet connector), this will help us see whether it boots at all and where the boot stops.
Another good idea for diagnostic is measuring with multimeter or voltage meter, for example at the GPIO headers if the is 5V DC when the board is powered, and track where the voltage disappears between the power jack and the main chip.
#6
A20 / Re: LIME2-4GB dead or not?
Last post by philderv - August 20, 2026, 05:39:08 PMOK
F3 tests are good
SD Card created with Olimex last image by Balena Etcher
Tried to boot the image on my LIME2: no luck
Can I affirm it is really dead?
F3 tests are good
SD Card created with Olimex last image by Balena Etcher
Tried to boot the image on my LIME2: no luck
Can I affirm it is really dead?
#7
A20 / Re: Working Linux driver for U...
Last post by sasha2002 - August 20, 2026, 01:41:55 PMTested this specific version of driver, it's not working.
At first you can't install it because it's not compiling at all with existing headers, downloaded from kernel.org, after compiling and modprobe
As you can see from /usr/lib/udev/rules.d/aic.rules :
I've added, but no luck :
At first you can't install it because it's not compiling at all with existing headers, downloaded from kernel.org, after compiling and modprobe
As you can see from /usr/lib/udev/rules.d/aic.rules :
Code Select
# AIC8800 USB mass-storage mode switch rules
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5721", SYMLINK+="aicudisk", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5722", SYMLINK+="aicudisk", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5723", SYMLINK+="tendaudisk", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5724", SYMLINK+="ugreenax900", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5725", SYMLINK+="tendaudiskv2", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5726", SYMLINK+="tendaudiskv3", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="5727", SYMLINK+="tendaudiskv4", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="572a", SYMLINK+="tendaudiskv5", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="572c", SYMLINK+="cudydiskv2", RUN+="/usr/bin/eject /dev/%k"
KERNEL=="sd*", ATTRS{idVendor}=="a69c", ATTRS{idProduct}=="572f", SYMLINK+="aicudisk572f", RUN+="/usr/bin/eject /dev/%k"
# AIC8800D80 "Pandora" clone: switch 1111:1111 to its operational USB ID.
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1111", ATTR{idProduct}=="1111", RUN+="/bin/sh -c 'if [ -x /usr/sbin/usb_modeswitch ]; then exec /usr/sbin/usb_modeswitch -c /etc/usb_modes>
There are no ID 350b:f179 or ID 350b:9612I've added, but no luck :
Code Select
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="350b", ATTR{idProduct}=="f179", RUN+="/usr/sbin/usb_modeswitch -v 0x350b -p 0xf179 -KW"
As i understand this driver is for other dongles #8
A20 / Re: LIME2-4GB dead or not?
Last post by LubOlimex - August 18, 2026, 04:40:11 PMNo idea, I've only used Balena Etcher and USBImager to prepare the images and then "dd" in the command line. Try with either Balena Etcher or USBImager both have Linux releases.
#9
A20 / Re: Working Linux driver for U...
Last post by LubOlimex - August 18, 2026, 04:37:35 PMFor Linux use the drivers and instructions at this GitHub article:
https://github.com/shenmintao/aic8800d80
Try something like:
https://github.com/shenmintao/aic8800d80
Try something like:
Code Select
sudo apt install git dkms build-essential linux-headers-$(uname -r) eject usb-modeswitch
git clone https://github.com/shenmintao/aic8800d80.git
cd aic8800d80
sudo ./install.sh
sudo reboot #10
FPGA / Re: Olimex GateMateA1-EVB + On...
Last post by LubOlimex - August 18, 2026, 03:38:12 PMWell if your FPGA bit stream implements UART and maps it to RP2040 debug-UART pins, it should.