- Welcome to Olimex Support Forum.
Olimex Support Forum
Recent posts
#1
Neo6502 / Re: Prophet server for the Neo...
Last post by Ralf - October 16, 2026, 07:18:57 PMDude!
Your Trinity Firmware is the hottest thing for the Neo6502 since the original Prophet-Server!
Two things I noticed:
- the Olimex UART WiFi Card seems not to be supported. Fair enough, you offer a viable alternative. However, I guess you might want to state that more clearly somewhere. First boot of Trinity with the UART Card inserted resulted in a myriad of error messages and lots of unwanted files suddenly appearing on my USB drive.
- how is the state of the keymap support? Can I change to a German keymap already?
I must confess, I was skeptical at first, but then I found that NeoBASIC is still provided, and Wolfenstein 3d is a marvel in itself!
Absolutely love the name, by the way: Trinity! So fitting for the whole project, very nice.
Great work!
Cheers
Your Trinity Firmware is the hottest thing for the Neo6502 since the original Prophet-Server!
Two things I noticed:
- the Olimex UART WiFi Card seems not to be supported. Fair enough, you offer a viable alternative. However, I guess you might want to state that more clearly somewhere. First boot of Trinity with the UART Card inserted resulted in a myriad of error messages and lots of unwanted files suddenly appearing on my USB drive.
- how is the state of the keymap support? Can I change to a German keymap already?
I must confess, I was skeptical at first, but then I found that NeoBASIC is still provided, and Wolfenstein 3d is a marvel in itself!
Absolutely love the name, by the way: Trinity! So fitting for the whole project, very nice.
Great work!
Cheers
#2
A20 / Re: Wich board to correctly mo...
Last post by oly - October 16, 2026, 04:25:07 PMI replace the non SPI board with the SPI embendded one.
I burnt again the OlinuXino image on the SD card.
I pluged the SD card in the new board (with the initial HDD connected) and powered on.
The prompt displays the hostname set during the previous installation ...
Seems that OS is loaded from HHD.
What should I do in order to properly reset the all so that I can boot from the OS on the SD card then execute the tool olinuxino-sd-to-sata from it toward the HDD ?
Noted that during the first try on the previous board, the olinuxino-sd-to-sata tool transfers OS to the HDD then displayed an error regarding the absence of SPI where to copy the bootloader.
I burnt again the OlinuXino image on the SD card.
I pluged the SD card in the new board (with the initial HDD connected) and powered on.
The prompt displays the hostname set during the previous installation ...
Seems that OS is loaded from HHD.
What should I do in order to properly reset the all so that I can boot from the OS on the SD card then execute the tool olinuxino-sd-to-sata from it toward the HDD ?
Noted that during the first try on the previous board, the olinuxino-sd-to-sata tool transfers OS to the HDD then displayed an error regarding the absence of SPI where to copy the bootloader.
#3
A64 / Re: Use USB OTG in host mode
Last post by LubOlimex - October 16, 2026, 12:01:36 PMTested solution: A64-OLinuXino-1Ge4GW USB OTG with OLIMAGE
We reproduced the problem on A64-OLinuXino-1Ge4GW with kernel 5.10.180-olimex and found the cause.
It is possible to restore safe dual-role operation without rebuilding the complete image. We tested both USB-device mode and USB-host mode.
What is wrong
USB0 PHY0 is shared by MUSB, EHCI0 and OHCI0. The current device tree assigns PHY0 to all three controllers. During boot, EHCI0/OHCI0 requests host mode for PHY0. The sun4i PHY driver then stops following the USB0 ID pin, so normal OTG role switching fails.
The device-tree correction is:
Installation
Download install-a64-olinuxino-usb0-dual-role.sh. Log in as root and run:
If the script reports that the DTB was installed and the FIT image was rebuilt, disconnect everything from the micro-USB socket and reboot:
The script verifies the board, creates backups, modifies and checks a temporary DTB, installs it, and rebuilds /boot/kernel.itb.
It also generates the complete readable DTS here:
Generating the full DTS from the installed DTB is safer than distributing one hard-coded DTS, since phandles and other definitions can change between OLIMAGE kernel packages.
Important limitation
For the moment, boot with the micro-USB socket empty. After Linux has started, insert the OTG adapter.
If the adapter is already inserted during boot, the kernel detects the host role but does not initially enable VBUS. Removing and reinserting the adapter fixes it. This remaining boot-time problem requires a small MUSB driver correction; it cannot be fixed completely by the DTS alone.
Test results
Quick check
With the OTG socket empty:
Expected result:
After Linux has booted, insert the OTG adapter and check:
The attached detailed guide contains the manual procedure and recovery commands.
Permanent OLIMAGE fix
The OLIMAGE kernel package should eventually include both corrections:
After that, users should receive the complete fix normally through apt update, apt dist-upgrade, u-boot-install and reboot.
Until the fix is included in OLIMAGE, a future kernel package upgrade can replace the manually corrected DTB, in which case the workaround must be applied again.
We reproduced the problem on A64-OLinuXino-1Ge4GW with kernel 5.10.180-olimex and found the cause.
It is possible to restore safe dual-role operation without rebuilding the complete image. We tested both USB-device mode and USB-host mode.
What is wrong
USB0 PHY0 is shared by MUSB, EHCI0 and OHCI0. The current device tree assigns PHY0 to all three controllers. During boot, EHCI0/OHCI0 requests host mode for PHY0. The sun4i PHY driver then stops following the USB0 ID pin, so normal OTG role switching fails.
The device-tree correction is:
- MUSB remains connected to PHY0 and remains in "otg" mode.
- The "phys" and "phy-names" properties are removed only from EHCI0 and OHCI0.
- The USB0 VBUS regulator is not forced permanently on.
Installation
Download install-a64-olinuxino-usb0-dual-role.sh. Log in as root and run:
Code Select
cd /root
wget https://ftp.olimex.com/TEMP/A64-OTG-fix/install-a64-olinuxino-usb0-dual-role.sh
chmod 700 /root/install-a64-olinuxino-usb0-dual-role.sh
/root/install-a64-olinuxino-usb0-dual-role.sh
If the script reports that the DTB was installed and the FIT image was rebuilt, disconnect everything from the micro-USB socket and reboot:
Code Select
reboot
The script verifies the board, creates backups, modifies and checks a temporary DTB, installs it, and rebuilds /boot/kernel.itb.
It also generates the complete readable DTS here:
Code Select
/root/sun50i-a64-olinuxino-1Ge4GW-usb0-dual-role.dts
Generating the full DTS from the installed DTB is safer than distributing one hard-coded DTS, since phandles and other definitions can change between OLIMAGE kernel packages.
Important limitation
For the moment, boot with the micro-USB socket empty. After Linux has started, insert the OTG adapter.
If the adapter is already inserted during boot, the kernel detects the host role but does not initially enable VBUS. Removing and reinserting the adapter fixes it. This remaining boot-time problem requires a small MUSB driver correction; it cannot be fixed completely by the DTS alone.
Test results
- Normal cable to a PC: USB peripheral mode worked, and the board did not drive VBUS.
- OTG adapter inserted after boot: host mode selected and VBUS enabled automatically.
- Low-speed USB mouse enumerated through OHCI0.
- High-speed SanDisk flash drive enumerated through EHCI0 as /dev/sda.
- Removing the OTG adapter disabled VBUS and returned USB0 to the idle role.
Quick check
With the OTG socket empty:
Code Select
cat /sys/class/extcon/extcon0/state
Expected result:
Code Select
USB=0
USB-HOST=0
After Linux has booted, insert the OTG adapter and check:
Code Select
cat /sys/class/extcon/extcon0/state
lsusb -t
dmesg | tail -n 30
The attached detailed guide contains the manual procedure and recovery commands.
Permanent OLIMAGE fix
The OLIMAGE kernel package should eventually include both corrections:
- Remove the EHCI0/OHCI0 PHY0 claims from the A64-OLinuXino device tree, leaving MUSB responsible for PHY0.
- Make the sunxi MUSB driver synchronize the existing USB-HOST extcon state when it starts, so booting with an OTG adapter already inserted also works.
After that, users should receive the complete fix normally through apt update, apt dist-upgrade, u-boot-install and reboot.
Until the fix is included in OLIMAGE, a future kernel package upgrade can replace the manually corrected DTB, in which case the workaround must be applied again.
#4
ESP32 / 3D print files for the DIN-RAI...
Last post by Rasp - October 16, 2026, 12:26:44 AM@LubOlimex, would it be possible to release/publish the 3D print files for the DIN-RAIL Plastic Seat of the ESP32-POE series?
It's very well designed and I love make a customized version for it that can also hold the MOD-IO2 board. I am happy to publicly share the finished result of cours
I apologize if this isn't the right forum section to ask.
It's very well designed and I love make a customized version for it that can also hold the MOD-IO2 board. I am happy to publicly share the finished result of cours
I apologize if this isn't the right forum section to ask.
#5
A64 / Re: Use USB OTG in host mode
Last post by winfried - October 15, 2026, 11:55:08 AMThanks, will wait for your result.
Just for info:
Also tried to disable the <®_drivevbus> for the _vbus-supply ind dts, but didnt help.
mfg winfried
Just for info:
Also tried to disable the <®_drivevbus> for the _vbus-supply ind dts, but didnt help.
Code Select
&usbphy {
status = "okay";
usb0_id_det-gpios = <&pio 7 9 GPIO_ACTIVE_HIGH>; /* PH9 */
usb0_vbus_det-gpios = <&pio 7 6 GPIO_ACTIVE_HIGH>; /* PH6 */
usb0_vbus-supply = <>; /* Remove or disable ID pin detection if it forces power-off */
usb1_vbus-supply = <®_usb1_vbus>;
};
mfg winfried
#6
A64 / Re: Use USB OTG in host mode
Last post by LubOlimex - October 15, 2026, 10:08:04 AMThe problem is the powering. I used AI to analyze what can be done and got it working if I force it in host mode but that is dangerous (in case you want device mode at some point). I will see if I can get it working properly in dual mode and will give you some instructions.
#7
New Product Ideas / pico-class on the Olimex RP204...
Last post by MikeVeng73 - October 15, 2026, 08:47:05 AMMay be it will be interresting for somebody:
https://github.com/DnCraptor/pico-class/
it contains Russion and English readme. For main topics (program modules) - let use online translator or AI.
Actually all required already done (see https://github.com/DnCraptor/pico-class/tree/main/hardware/olimex-pico-pc), so, it is just to highlight that it exists, and may be useful for Olimex customers.
https://github.com/DnCraptor/pico-class/
it contains Russion and English readme. For main topics (program modules) - let use online translator or AI.
Actually all required already done (see https://github.com/DnCraptor/pico-class/tree/main/hardware/olimex-pico-pc), so, it is just to highlight that it exists, and may be useful for Olimex customers.
#8
A64 / Re: Use USB OTG in host mode
Last post by winfried - October 15, 2026, 12:40:45 AMFirst report:
- Measured that the USB-OTG Pin is set to GND with OTG cable and made the mouse test. So the OTG functionality seems to be broken.
Changed the devicetree:
Result:
3 seconds after boot mouse is detected and is powered and after 33 second usb0-vbus is disabled and mouse is disconnected. So there is somewhere a timeout or the like.
Suspected the autosuspend, disabling, but still something in the system switches of the usb0-vbus, so disabled "USB Autosuspend" in Linux (Runtime Power Management).
in /boot/uEnv.txt put the line
What also is suspect is that there is a
So I stop for today, any hint is welcome
- Measured that the USB-OTG Pin is set to GND with OTG cable and made the mouse test. So the OTG functionality seems to be broken.
Changed the devicetree:
Code Select
&usb_otg {
dr_mode = "host"; /* set to host from otg */
status = "okay";
};
Result:
3 seconds after boot mouse is detected and is powered and after 33 second usb0-vbus is disabled and mouse is disconnected. So there is somewhere a timeout or the like.
Suspected the autosuspend, disabling, but still something in the system switches of the usb0-vbus, so disabled "USB Autosuspend" in Linux (Runtime Power Management).
in /boot/uEnv.txt put the line
Code Select
optargs=usbcore.autosuspend=-1but this did not help.What also is suspect is that there is a
Code Select
/sys/devices/platform/usb1-vbusbut noCode Select
/sys/devices/platform/usb0-vbusSo I stop for today, any hint is welcome
#9
A20 / Re: Wich board to correctly mo...
Last post by oly - October 14, 2026, 01:48:46 PMThank you for clarifications.
#10
A20 / Re: Wich board to correctly mo...
Last post by LubOlimex - October 14, 2026, 08:25:56 AMYes. This is expected behavior. The T2/A20 Boot ROM cannot boot directly from SATA. Its supported boot sources are SD/MMC, NAND, SPI NOR, and USB/FEL—SATA is absent. So you need a middle storage medium for the u-boot (SD/MMC, NAND, SPI NOR, and USB/FEL—SATA) between the main chip T2/A20 BROM and the SATA hard-disk.
Boards without 16MB SPI flash aka "-s16M" can't boot directly into the hard disk without the help of additional storage (either SD card or SPI flash). The U-Boot is too big to be stored on the EEPROM!
So options are - get "s16M" variant, or use SD card only for the U-Boot. USB/FEL—SATA doesn't appear like viable option since this requires another computer running sunxi-fel uploading the U-Boot on every cold boot. Same for NAND, NAND is not supported by mainline, and if you use eMMC an extra step through the EEPROM is needed, and our software doesn't support that option.
Boards without 16MB SPI flash aka "-s16M" can't boot directly into the hard disk without the help of additional storage (either SD card or SPI flash). The U-Boot is too big to be stored on the EEPROM!
So options are - get "s16M" variant, or use SD card only for the U-Boot. USB/FEL—SATA doesn't appear like viable option since this requires another computer running sunxi-fel uploading the U-Boot on every cold boot. Same for NAND, NAND is not supported by mainline, and if you use eMMC an extra step through the EEPROM is needed, and our software doesn't support that option.