Recent posts

#11

ARDUINO / Re: Discharged batteries JA-80...

Last post by LubOlimex - November 24, 2025, 10:14:52 AM

They need more time. Leave them connected for 24h and check again. If the voltage stays 0.1V after 24h of charging they are probably very dead.

#12

ESP32 / Re: Very weird blown capacitor...

Last post by LubOlimex - November 24, 2025, 09:59:29 AM

Thanks for the feedback. We always improve on our designs, they are not set in stone, sadly we can't emulate scenarios and all problems here - sometimes we need customer feedback before we can spot a potential issue. We will bring some changes to the hardware design that should further reduce the chances of such a capacitor pop in the next hardware revision of ESP32-POE-ISO, e.g. hardware revision N.

#13

A64 / Re: eth0 disappears

Last post by LubOlimex - November 24, 2025, 08:38:54 AM

1. What is the state of the PHYRST1 PTH jumper? Is it closed or open? You also need to open that jumper in conjunction with running the script.

2. What exactly is the name and variant of the A64 board that you got (as printed on the box)? So I can test it myself.

#14

ESP32 / Re: Very weird blown capacitor...

Last post by slacks33 - November 24, 2025, 06:03:45 AM

Oh well, that is quite interesting. Thanks for the feedback. First time see something like this and we've manufactured quite a few of these boards. These are 4-layer boards heat dissipation should be quite good. A lot of customers used it in harsh conditions and never reported such a problem, it is either they didn't report it or something in your design is harsher. Good news is that revision B is quite old revision. Currently manufactured boards would behave quite differently since that part of the board was redesigned with different DC-DC. I would suggest latest revision of the board would be better for heat dissipation.

Hey there, don't mean to necropost, but I ran across this thread having the exact same issue on a ESP32-POE-ISO-EA-IND.

Bought this board in January of 2024, it has been running in a climate controlled room since shortly after that date. It has been largely untouched since then, I pulled it out to put it in a new 3D Printed case, just to find this:


This is Revision L, so I'm surprised that this is still happening. Reached out to support a few minutes ago, just wanted to also add to my findings here. Hoping this can get resolved, spent the extra money on the IND version to ensure I would have great longevity with this product.

#15

A20 / Re: A20-OLinuXino-MICRO ILITEK...

Last post by Globici - November 23, 2025, 04:58:00 PM

I've recompiled the kernel and managed to get it working with :

Code Select Expand

/dts-v1/;
/plugin/;

/ {
        compatible = "allwinner,sun7i-a20";

        fragment@0 {
                target = <&i2c0>;
                __overlay__ {
                        #address-cells = <1>;
                        #size-cells = <0>;
                        status = "okay";

                        ili210x@41 {
                                compatible = "ilitek,ili210x";
                                reg = <0x41>;
                                touchscreen-size-x = <0x320>;
                                touchscreen-size-y = <0x1e0>;
                                interrupt-parent = <&pio>;
                                interrupts = <8 14 2>; /* PI14, IRQ_TYPE_EDGE_FALLING */
                                reset-gpios = <&pio 4 2 1>; /* PE2, GPIO_ACTIVE_LOW */
                                touchscreen-swapped-x-y;
                                touchscreen-inverted-y;
                                wakeup-source;
                        };
                };
        };
};

but the TAP does not work (well, it works but if I place my finger in the middle of the screen the cursor is moved under my finger but the TAP is happening on the bottom of the screen ... idk why).

#16

ARDUINO / Discharged batteries JA-803450...

Last post by binutzu - November 23, 2025, 12:15:23 PM

Hello,

i have two JA-803450P batteries, one from EduArdu and one from Lime2 home server.
They stayed long time unused.
Lately i needed EduArdu as remote control and tried to charge one of them.
However, they do not seem to charge in 1-2h at all.
The measured voltage is v. v. low: 0.1V

The spec https://www.olimex.com/Products/Power-Supply/Lipo-battery/BATTERY-LIPO1400mAh/resources/JA803450-Spec-Data-Sheet--J-A.pdf
mentions in §8.7 and §8.8 "charging from 0" respectively after long time.
Is there a way to re-charge them using EduArdu or Lime2 or is special gear required?

Otherwise, they are due for recycling ...

Thanks in advance.

#17

A64 / Re: eth0 disappears

Last post by frm - November 22, 2025, 02:29:02 AM

I can copy here also the boot log taken from UART:

Code Select Expand

U-Boot SPL 2021.04+olimex-1-20231103.141125 (Nov 03 2023 - 14:12:49 +0000)
DRAM: 1024 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.0(debug):
NOTICE:  BL31: Built : 23:33:29, Nov 27 2018
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x40b18b8, model: Olimex A64-Olinuxino-eMMC
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
NOTICE:  BL31: PMIC: Detected AXP803 on RSB.
INFO:    PMIC: AXP803: Enabling DRIVEVBUS
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9


U-Boot 2021.04+olimex-1-20231103.141125 (Nov 03 2023 - 14:12:49 +0000) Allwinner Technology

CPU:   Allwinner A64 (SUN50I)
Model: Olimex A64-Olinuxino-eMMC
DRAM:  1 GiB
MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from EXT4... *** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Allwinner mUSB OTG (Peripheral)
Net:   phy interface7
Could not get PHY for ethernet@1c30000: addr 1
eth1: usb_ether
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 2 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
2274 bytes read in 3 ms (740.2 KiB/s)
## Executing script at 4fc00000
U-boot loaded from SD
Boot script loaded from mmc
Checking for /uEnv.txt...
Checking for /boot/uEnv.txt...
460 bytes read in 2 ms (224.6 KiB/s)
Loaded environment from /boot/uEnv.txt
Loading FIT image...
30553463 bytes read in 1308 ms (22.3 MiB/s)
## Loading kernel from FIT Image at 58000000 ...
   Using 'config-8367' configuration
   Trying 'kernel-1' kernel subimage
     Description:  Linux kernel 5.10.180-olimex
     Type:         Kernel Image
     Compression:  uncompressed
     Data Start:   0x580000d4
     Data Size:    20115464 Bytes = 19.2 MiB
     Architecture: AArch64
     OS:           Linux
     Load Address: 0x40080000
     Entry Point:  0x40080000
     Hash algo:    crc32
     Hash value:   b03bc58f
     Hash algo:    sha1
     Hash value:   5e019dd581acd68089a70153bfd56c3f01bd1b47
   Verifying Hash Integrity ... crc32+ sha1+ OK
## Loading ramdisk from FIT Image at 58000000 ...
....

I guess that "Could not get PHY for ethernet@1c30000: addr 1" might be a sign of an HW issue?
If that's the case I hope I can return the board and get a new one cause it's fresh new.

#18

A64 / eth0 disappears

Last post by frm - November 22, 2025, 02:15:28 AM

Hi all,
I just unboxed my shiny new A64, imaged with the "A64-OLinuXino-bullseye-base-20231106-081613.img" image (stored on SD card).
I do have also the MOD-WIFI-RTL8188EUS-ANT part, so I expect to have 2 ethernet interface: the wired RJ45 eth interface and the wireless one.

Surprisingly, the first one is what's giving me troubles (wired Eth interface).
On the first boot I actually did have "eth0". Then I think I rebooted after reading a message about the DTS tree initial setup being completed (IIRC).
After reboot eth0 was disappeared. I read some thread about Eth interface being multiplexed with the LCD display so I used the "olinuxino-display" utility to set LCD mode to DISABLED. Reboot. Eth0 was there.

Now after another reboot eth0 is gone again.
I tried again to set LCD to DISABLED with "olinuxino-display" and rebooted. Eth0 is still not there.
This is what I see in kernel log:

Code Select Expand

# dmesg | grep -i ethernet
[    1.309067] dwmac-sun8i 1c30000.ethernet: IRQ eth_wake_irq not found
[    1.309076] dwmac-sun8i 1c30000.ethernet: IRQ eth_lpi not found
[    1.309490] dwmac-sun8i 1c30000.ethernet: PTP uses main clock
[    1.309513] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 1806 (expect 0)
[    1.309782] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported
[    1.309790] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported
[    1.309797] dwmac-sun8i 1c30000.ethernet: COE Type 2
[    1.309803] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported
[    1.309809] dwmac-sun8i 1c30000.ethernet: Normal descriptors
[    1.309816] dwmac-sun8i 1c30000.ethernet: Chain mode enabled
[    1.418776] dwmac-sun8i 1c30000.ethernet: EMAC reset timeout
[    1.424451] dwmac-sun8i 1c30000.ethernet eth0: stmmac_dvr_remove: removing driver
[    1.440228] dwmac-sun8i: probe of 1c30000.ethernet failed with error -110

my kernel is:

Code Select Expand

# uname -a
Linux viesmann-olinuxino 5.10.180-olimex #092646 SMP Tue Jul 25 09:28:50 UTC 2023 aarch64 GNU/Linux

is this a known issue?

#19

A20 / Re: A20-OLinuXino-MICRO ILITEK...

Last post by Globici - November 21, 2025, 09:23:37 PM

It seems like

Code Select Expand

  olimage.core.setup.kernel:
    modules:
      blacklist:
        - sun4i_gpadc_iio
        - sun4i_gpadc
      enable:
        - g_serial
        - sun4i_ts
        - ili210x
should work but it doesn't.

If I rebuild the kernel with the driver would it work ?

#20

Neo6502 / Re: Trouble flashing firmware ...

Last post by LubOlimex - November 21, 2025, 11:17:50 AM

Which USB connector and what USB cable do you use? You need USB type C for powering and USB type A for downloading new software, cable like this:

https://www.olimex.com/Products/Components/Cables/USB/USB-CABLE-AM-AM/

You disconnect the power supply USB-C cable, then press the BOOT button and plug the USB-A cable to USB host connector. Your computer will show a new drive. Once this new drive shows copy the .uf2 file to it. Once the firmware is programmed the drive will disappear. This means the RP2040 now has the new firmware loaded.