[GA36-MB V1.2-20260416 / Allwinner A23] (Xeno) USB OTG not working under GoodLuckOS – FEL mode works without SD card
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- linux, operating-systems
- Domaine
- embedded-iot
Piste de recherche
Start by comparing the USB configuration for the GA36-MB V1.2 and Allwinner A23 with the related A33 report in issue #91. The issue points to USB PHY initialization, USB0 role configuration, GPIO/VBUS settings, and device-tree or FEX configuration, but does not name the relevant files or tests. Done means USB peripherals enumerate reliably in host mode; gadget mode is a separate goal to verify.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Device Information
- Device: R36S / GA36 clone
- Motherboard: GA36-MB V1.2
- SoC: Allwinner A23 (ARMv7, 32-bit)
- RAM: 512 MB DDR3 (2 RAM chips)
- Operating System: GoodLuckOS
- Original Firmware: EmuELEC-based firmware (marketed as ArkOS 2.0)
- Original Kernel: Linux 3.4.39
- GoodLuckOS Kernel (previously tested): 7.2.9-dirty
- USB Ports: Two USB-C connectors (charging and OTG)
Problem Description
I have been investigating USB OTG functionality on my GA36-MB V1.2 motherboard with an Allwinner A23 processor and 512 MB RAM, running GoodLuckOS.
GoodLuckOS boots successfully, and almost all essential hardware functions work correctly. However, USB connectivity does not function as expected.
Neither USB host mode nor USB device/gadget mode has worked successfully during our tests.
The most important finding is that USB FEL mode works when the SD card is removed, but the computer no longer detects the console once GoodLuckOS boots.
This suggests a possible USB initialization or configuration issue rather than a completely nonfunctional physical USB data connection.
Working Hardware and Features
The following features work correctly under GoodLuckOS:
- Display: Working correctly.
- Physical buttons and D-pad: Working.
- Audio output: Working.
- Volume controls: Working.
- Screen brightness adjustment: Working.
- EmulationStation: Working.
- RetroArch: Working.
- Game emulation: Working.
The system is usable for gaming. The primary unresolved connectivity issue is USB OTG.
I wanted to highlight these working features because they may help narrow down the problem to USB-specific initialization or configuration rather than a broader hardware compatibility issue.
Important Discovery: FEL Mode Works Without the SD Card
We performed two tests using the same console and USB connection.
Test 1 – Without SD Card
- Removed the SD card from the console.
- Connected the console to a computer through the USB data port.
- The console entered Allwinner FEL mode.
- The computer successfully detected the device.
Result: SUCCESS
Test 2 – With GoodLuckOS Running
- Inserted the GoodLuckOS SD card.
- Booted the console normally.
- Connected the console to the same computer through the same USB connection.
- The computer did not detect a USB device.
Result: FAILED
This confirms that USB data communication works at least at the SoC BootROM/FEL level, although it does not establish that USB host mode works.
The difference suggests a possible USB controller, PHY, GPIO, or operating-system configuration issue.
USB Tests Performed
- FEL mode without SD card: Working.
- PC connection with GoodLuckOS running: Not detected.
- USB flash drive: Not detected.
- USB mouse: Not detected.
- USB Wi-Fi adapter: Not detected.
- DualShock 4 via USB: No reliable connection.
- Android phone via USB-C: No response.
- Android USB tethering: Not working.
- USB OTG adapters: Not working.
- Externally powered USB hub/adapter: No successful USB enumeration.
Additional USB Test Observations
During one test, the DualShock 4 controller name appeared, but we could not reproduce reliable functionality.
An externally powered adapter illuminated a USB flash drive's LED, but USB data communication was not established.
This does not establish that the console itself provides sufficient VBUS power.
USB Diagnostics
Running lsusb generally showed only the internal USB root hub:
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
No external USB peripherals appeared during the unsuccessful tests.
Kernel Messages
During testing, we observed:
platform is usb host
Set USB Power ON
get usbc(0) det_vbus gpio failed
These messages suggest that the kernel attempts to initialize USB host mode.
However, they do not confirm that physical VBUS power is present at the connector or that the USB PHY and data lines are correctly configured.
GPIO Observations
We also observed:
otg_id input low
otg_drv_vbus output high
These GPIO states may be relevant to USB role detection and VBUS power control.
Kernel Configuration Observations
The tested kernel configuration contained the following USB-related options:
CONFIG_USB_SUNXI_USB0_OTG=y
CONFIG_USB_STORAGE=y
CONFIG_USB_HID=y
However, we could not find the following option:
CONFIG_USB_NET_RNDIS_HOST
Missing RNDIS host support could explain why Android USB tethering is unavailable, but it would not explain the failure to enumerate USB storage devices, mice, or other standard USB peripherals.
Additional Observations
- The motherboard is GA36-MB V1.2, using the Allwinner A23 SoC and 512 MB DDR3 RAM.
- The console has two USB-C connectors.
- The original EmuELEC-based firmware also exhibited USB connectivity issues.
- GoodLuckOS successfully operates the display, physical buttons, audio, volume controls, and screen brightness controls.
- EmulationStation and RetroArch work.
- The kernel appears to attempt USB host initialization.
- External USB peripherals are not successfully enumerated.
- USB FEL mode works without the SD card.
- USB communication with a computer fails after GoodLuckOS boots.
- Both USB host and USB gadget functionality may be affected.
Possible Causes to Investigate
Based on the observations, the following areas may be worth checking:
- Allwinner A23 USB PHY initialization.
- USB0 host/device/OTG configuration.
- USB ID detection GPIO assignments.
- VBUS power control and detection.
- Device-tree or FEX configuration for the GA36-MB V1.2 motherboard.
- Differences between A23 and A33 USB configurations.
- Missing USB gadget functionality in GoodLuckOS.
- USB role switching during Linux initialization.
Questions for the Developers
- Is USB OTG currently supported on the GA36-MB V1.2 motherboard with the Allwinner A23 SoC and 512 MB RAM?
- Since FEL mode works without the SD card, could the issue be related to USB initialization after Linux boots?
- Are there specific USB GPIO, VBUS, or USB PHY settings required for this motherboard revision?
- Are there known differences between A23 and A33 boards regarding USB controller configuration?
- Does the current GoodLuckOS build include functional USB host and gadget support?
- Could building GoodLuckOS from the latest source resolve the problem?
- What additional kernel logs, device-tree parameters, FEX configurations, or hardware information would help diagnose this issue?
Related Issue
I found a similar report involving an Allwinner A33-based device:
https://github.com/CodeZombie/goodluckOS/issues/91
However, my device uses an Allwinner A23 on a GA36-MB V1.2 motherboard, so this could be a separate board-specific issue.
Goal
My main objective is to enable reliable USB host functionality for:
- USB flash drives
- USB game controllers
- USB Wi-Fi adapters
- USB Ethernet adapters
- Android USB tethering
I would also like to investigate whether USB gadget mode can be enabled for connecting the console directly to a computer.
I can provide additional kernel logs, hardware photos, configuration files, and diagnostic results if needed.
Thank you for developing GoodLuckOS and supporting these unusual clone devices!
- Langage dominant
- C++
- Étoiles
- 54
- Forks
- 8
- Merge moyen
- 16 j 19 h
- PR mergées (30 j)
- 4
Préparer son environnement
Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de CodeZombie/goodluckOS
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 65/100
CodeZombie/goodluckOS#178 ·
-
TODO
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
CodeZombie/goodluckOS#12 ·
-
memory space or gamesOuverte
Difficulté 3/5 1-2 jours Accessibilité débutants 35/100
CodeZombie/goodluckOS#177 · 1 commentaire ·
-
ME SALE SOFWARE DESCONOCIDOOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 25/100
CodeZombie/goodluckOS#176 ·
-
Appropriate names for gamesOuverte
Difficulté 3/5 1-2 jours Accessibilité débutants 54/100
CodeZombie/goodluckOS#174 · 1 commentaire ·
Toutes les issues de CodeZombie/goodluckOS
Issues similaires
-
needs-format
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
Niko1221/Strata#6251 · 1 commentaire ·
Les mainteneurs répondent en général sous 5 jours
-
[Bug]: NP 管理器文件编辑器里删除键无效Ouvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
metasequoiaime/msime#11666 ·
Les mainteneurs répondent en général sous 1 jour
-
DAE2 crashes on call.without.effects with a non ref.func expressionPeut-être pris @stevenfontanella l’a pris aujourd’hui. Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
WebAssembly/binaryen#9404 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
CVO-Org/immersive-cigs-rewrite#313 ·
Les mainteneurs répondent en général sous 1 jour
-
windows-latest (20261116.315.1) ships with incompatible MSVC (18.12) and pinned LLVM/Clang (20)Ouvertebug report
Difficulté 2/5 1-3 heures Accessibilité débutants 73/100
actions/runner-images#15367 · 4 commentaires ·
Les mainteneurs répondent en général sous 2 jours