Recent posts

#1

FPGA / SPI Programming Sequence for i...

Last post by cdan - April 03, 2026, 01:04:38 PM

I am using an external programmer (pico-serprog) to program the iCE40HX8K via SPI. Programming only works if C_RESET is pulled LOW before powering on the board. If C_RESET is pulled LOW after power is already applied, SPI communication fails.

Can you confirm: When C_RESET is pulled LOW while the board is already powered on, do the SDI, SDO, and SCK pins on the FPGA chip enter high-impedance (Hi-Z) state? Is there a specific reset/power-on sequence required for the iCE40 to enter SPI programming mode?

#2

ESP32 / Re: Demo Code for ESP32-P4-Dev...

Last post by lph65724 - March 30, 2026, 04:57:56 AM

Thank you

#3

ESP32 / Re: Demo Code for ESP32-P4-Dev...

Last post by LubOlimex - March 23, 2026, 11:18:41 AM

This demo works 100%: https://github.com/OLIMEX/ESP32-P4-DevKit/tree/main/SOFTWARE/Demo_Examples/display_lvgl_demos

#4

ESP32 / Demo Code for ESP32-P4-DevKit ...

Last post by lph65724 - March 20, 2026, 10:52:28 AM

I just purchased a ESP32-P4_DevKit and a MIPI-HDMI, and I want to try to output some thing to a TV. Is there a demo code for me to try that?

Thank you

#5

A20 / Re: HDMI connection back feedi...

Last post by LubOlimex - March 19, 2026, 08:12:29 AM

Thank you for the update! Glad you fixed it, hopefully if another customer has similar issue will stumble on your post!

#6

A20 / Re: HDMI connection back feedi...

Last post by dry - March 19, 2026, 01:54:33 AM

I got this little adapter:
https://www.aliexpress.com/item/1005004985145407.html?spm=a2g0o.order_list.order_list_main.17.21ef1802VXeBN3#nav-specification

( ISHRIC VGA HDMI-compatible Virtual Display Adapter Dummy Plug Emulator Lock plate 4K Headless Ghost Display Emulator DDC Edid ).

..and no clue on details how its wired, but, all my tests so far it stops that leakage / backfeed.  no more leds on, no more voltage coming in from monitor. bah.

I did not want to un-solder stuff on my Oli board, in case i damage it, so this works better for me

#7

A20 / Re: HDMI connection back feedi...

Last post by dry - March 18, 2026, 03:20:49 AM

disable CEC mode

So i bought Lindy CEC less HDMI adapter, with no connection on pin 13.  The issue still persists,
still leaks...

Nothing to do seem with serial, no serial to usb connected.

So. HDMI feedsback in, but Not due to CEC ...

#8

ESP32 / Re: New ESP32-POE-ISO - was I ...

Last post by chrismacp - March 09, 2026, 05:49:51 PM

Okay, I managed to measure Pins 1 and 3, a little tricky indeed. I only got 0.2mV so I think that it's probably dead.

I'll try and replace it and see how it goes. I appreciate the help trying to fix this btw

#9

A64 / Re: Bookworm upgrade availabil...

Last post by mossroy - March 08, 2026, 09:06:47 PM

I ran some tests again on an Olinuxino A64-OLinuXino-2Ge8G-IND board, to see if there was a recent version of Linux I could install on it (supported after August 2026).

I tried armbian with Armbian_community_26.2.0-trunk.493_Lime-a64_trixie_current_6.12.74_minimal.img.xz image. It's not starting at all with error message: "Unhandled Exception in EL3.". And I saw nobody using this board in their forum.

I tried the Debian installer of Debian 13 "trixie" (https://deb.debian.org/debian/dists/stable/main/installer-arm64/current/images/netboot/SD-card-images/), dated 2026-01-05, with kernel 6.12.73. It can be installed with no issue and no trick. But, when restarting on the freshly installed OS, it hangs on "Starting kernel ...", with no visible error message.

Same result with the Debian installer of Debian unstable "sid" (https://d-i.debian.org/daily-images/arm64/daily/netboot/SD-card-images/), dated 2026-03-06, with kernel 6.12.73 too.

BUT I managed to make Debian Trixie start after forcing the kernel to use sun50i-a64-olinuxino-2Ge8G.dtb instead of the sun50i-a64-olinuxino.dtb (used by default by Debian on this board). It can be done by putting the file in dtbs/(latest kernel version)/allwinner directory of the boot partition, interrupting startup in u-boot, and typing these commands in u-boot:

Code Select Expand

setenv fdtfile allwinner/sun50i-a64-olinuxino-2Ge8G.dtb
boot

There are a few errors in the console, though:

Code Select Expand

[    7.561076] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    7.591996] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    7.827461] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    7.895088] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    7.951018] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    8.065466] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    8.401470] sun4i-usb-phy 1c19400.phy: Couldn't get regulator usb0_vbus... Deferring probe
[    8.589256] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.596088] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.602995] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.609826] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.617300] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.677685] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.684173] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    8.692755] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[    8.693185] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.706637] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.713384] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.720145] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.726914] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.733645] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.740131] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    8.748700] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[    8.756350] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.763198] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.770002] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.776754] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.783643] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.790533] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.797066] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    8.805658] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[    8.890938] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.897784] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.904617] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.911625] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.919850] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.926641] sunxi-mmc 1c11000.mmc: data error, sending stop command
[    8.933133] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[    8.941708] Buffer I/O error on dev mmcblk1, logical block 0, async page read
/dev/mmcblk0p3: clean, 80599/1733312 files, 777867/6925568 blocks
[   19.976565] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   19.983758] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   19.990588] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   19.997428] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.004302] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.011516] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.019379] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2
[   20.046176] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.053060] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.059950] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.066867] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.073885] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.080774] sunxi-mmc 1c11000.mmc: data error, sending stop command
[   20.087424] I/O error, dev mmcblk1, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2
[   20.095977] Buffer I/O error on dev mmcblk1, logical block 0, async page read
[   22.382242] sun8i-dw-hdmi 1ee0000.hdmi: Couldn't get the HDMI PHY
[   22.392831] sun4i-drm display-engine: Couldn't bind all pipelines components
[   22.764221] sun4i-i2s 1c22800.i2s: Missing dma channel for stream: 1
[   22.770765] sun4i-i2s 1c22800.i2s: ASoC: error at snd_soc_pcm_component_new on 1c22800.i2s: -22
[   22.779545] asoc-simple-card hdmi-sound: ASoC: can't create pcm 1c22800.i2s-i2s-hifi :-22
[   22.788273] asoc-simple-card hdmi-sound: probe with driver asoc-simple-card failed with error -22
It seems to work, even if I did not test more than a few hours. However, there are some issues:

- a few kernel crashes reported on the console. I did not see any visible consequence, though:

Code Select Expand

[ 1330.457436] INFO: task kworker/0:1H:153 blocked for more than 1208 seconds.
[ 1330.465883]       Tainted: G         C         6.12.73+deb13-arm64 #1 Debian 6.12.73-1
[ 1330.474004] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 1330.481915] task:kworker/0:1H    state:D stack:0     pid:153   tgid:153   ppid:2      flags:0x00000008
[ 1330.491353] Workqueue: mmc_complete mmc_blk_mq_complete_work
[ 1330.497120] Call trace:
[ 1330.499639]  __switch_to+0xf4/0x168
[ 1330.503200]  __schedule+0x398/0xf18
[ 1330.506748]  schedule+0x30/0x130
[ 1330.510036]  schedule_timeout+0x138/0x180
[ 1330.514103]  __wait_for_common+0xdc/0x270
[ 1330.518167]  wait_for_completion+0x28/0x40
[ 1330.522324]  mmc_wait_for_req_done+0x34/0x108
[ 1330.526738]  mmc_wait_for_req+0xb4/0x108
[ 1330.530712]  mmc_wait_for_cmd+0x70/0xb8
[ 1330.534596]  __mmc_send_status+0x80/0xd8
[ 1330.538575]  mmc_blk_mq_rw_recovery+0x60/0x3d8
[ 1330.543089]  mmc_blk_mq_poll_completion+0x80/0x220
[ 1330.547965]  mmc_blk_mq_complete_work+0x58/0x98
[ 1330.552575]  process_one_work+0x178/0x3e0
[ 1330.556652]  worker_thread+0x204/0x3f0
[ 1330.560475]  kthread+0xe8/0xf8
[ 1330.563599]  ret_from_fork+0x10/0x20- restarting the board does not work: it stops, the console displays "systemd-shutdown[1]: Syncing filesystems and block devices.", but the device does not restart
- running any command that triggers update-initramfs (like a kernel upgrade, or installing cryptsetup for example) ends up with an error "Unsupported platform 'Olimex A64-Olinuxino-2Ge8G-IND". That's because this dtb file refers to this model name, for which there is no dtb provided with Debian kernel, that provides only models "Olimex A64-Olinuxino" (sun50i-a64-olinuxino.dts) and "Olimex A64-Olinuxino-eMMC" (sun50i-a64-olinuxino-emmc.dts)

So it's not really usable for now. But, at least, there is some hope.

@Olimex: your help would be really welcome to find a sustainable way to use a regular Debian Trixie on this variant of Olinuxino A64. For example by providing an appropriate dtb, or a dtb overlay (dtbo) over one provided by Debian.

#10

A20 / Re: HDMI connection back feedi...

Last post by LubOlimex - March 06, 2026, 08:21:27 AM

Measure to see if the issue exists without the serial debug cable. Maybe try another serial debug cable, we've had similar problems in the past with some serial debug cables that might power the board parasitically from the data line (RX and TX).

If not consider other ways to debug the board like SSH or mini USB, as detailed in the manual:

https://raw.githubusercontent.com/OLIMEX/OLINUXINO/master/DOCUMENTS/OLIMAGE/Olimage-guide.pdf