Recent posts

#1

ESP32 / Re: ESP-POE having problems wi...

Last post by djpeterlewis - May 13, 2024, 11:21:47 PM

Maybe try with GPIO32 or GPIO33

I tried GPIO32 with the same result. A random flash , sometimes all 100 pixels and other times just a few, always White . WS2815B. I timed it to see if they were equally timed , but they are not

#2

ESP32 / Re: ESP-POE having problems wi...

Last post by djpeterlewis - May 13, 2024, 08:11:59 PM

It is the WROOM version. I did try GPIO15 and still had the same issue, will try he other ones and let you know. I believe it is the conversion between the Ethernet and the SPI output in WLED that is causing the issue.

The WLED code using their internal patterns do not show any issues.

#3

STMP1 / Re: Olimex STMP1 SOM - Error s...

Last post by Gaël - May 13, 2024, 12:24:28 PM

Hi,

> This is expected by design. All boards should fail to start if there was not enough time for the capacitors to discharge. There should be at least 2 seconds between power ups.

I didn't know this limitation. I can't use LiPo battery to protect boards against micro power cuts because LiPo are not safe enough in the hot environments where boards are used (wood boiler).

After some tests, I can't reproduce the problem with this image even with quick power cuts : good news !

But I have a lot of errors during the first 100 seconds after boot :

Code Select Expand

[   83.123763] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   83.846734] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   84.570037] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   85.293739] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   86.017742] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   86.741530] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   87.465436] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   88.188899] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   88.911906] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   89.700894] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   90.422235] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   91.143840] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   91.864692] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   92.585549] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   93.307060] es8328 0-0010: ASoC: error at snd_soc_component_update_bits on es8328.0-0010: -11
[   94.030435] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   94.752109] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   95.474055] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   96.196230] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   96.918255] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   97.640112] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   98.361737] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   99.082735] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[   99.804734] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  100.526133] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  101.247231] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  101.968004] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  102.688578] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
[  103.409249] es8328 0-0010: ASoC: error at soc_component_read_no_lock on es8328.0-0010: -11
And I have no network :

Code Select Expand

olimex@stm32mp1-olinuxino-som:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
olimex@stm32mp1-olinuxino-som:~$
Edit : I understand the error messages, the kernel has been made for SOM not for LIME.

#4

ESP32 / Re: ESP32 poe noise

Last post by LubOlimex - May 13, 2024, 11:43:45 AM

Where and how exactly do you measure this noise? Where do you attach your equipment, so we can test in same conditions.

#5

ESP32 / Re: ESP-POE having problems wi...

Last post by LubOlimex - May 13, 2024, 09:44:46 AM

First make sure you ESP32-POE board has WROOM module (e.g. it is NOT ESP32-POE-WROVER version). If it is WROOM version then GPIO16 is not used for the Ethernet. It goes to the UEXT and also has 2.2k pullup (visible near the UEXT). Did you try with other GPIO? Maybe try with GPIO32 or GPIO33 from the header, these have no pull ups (make sure to reflect the hardware change in code).

#6

ESP32 / ESP-POE having problems with D...

Last post by djpeterlewis - May 12, 2024, 11:12:05 PM

Hi,
I do not know if this is a problem using WLED or if they are using the wrong way of collecting data from the Ethernet port.

I am still having a problem with the OLIMEX  ESP-POE-EA Ethernet unit. I have Put in a Level Converter, I have changed the PSU for a different type, I put on a Power Surge/Suppression on the 220v Side, From the 12v Side I have 2 x 1000uf caps. The problem is random flashing of White , sometimes the whole 100 pixels and other times just a small section or 2. Running WS2815B 12v. It is only when I am using ARTNET. Tried Madrix and Jinx both on Blackout and this happens (it does also happen in patterns but not as noticeable). I also tried without ARTNET using the internal pattern on a single color and no problems, Even dimmed it to off on WLED and no problems. It seems like it is a Ethernet / ARTNET problem. Is there any way of creating a log file with timecode of the output GPIO values and also the Ethernet data ? Being intermittent and only happening sometimes 3 minutes apart and other times 45 second apart makes if difficult to pin point the issue. But so far is looks like from the Board to the Strips are perfect. Now I believe it is in the software, I have tried earlier versions and the very latest beta's same issue. In Madrix and JINX I also put the brightness to 0 instead of Blackout with still the same issue. I also turned on the setting for ignoring packets not in sequence. I have tried multiple boards. Using GPIO 16. I have just seen that the GPIO 16 is used by EMAC , so possible this might be the fault. I have a 5v BUC converter from the 12v line that feeds the OLIMEX ESP-POE
Any Thoughts Thank you.

#7

A64 / Re: Bookworm upgrade availabil...

Last post by mossroy - May 11, 2024, 02:57:23 PM

As for whom it may be relevant, now, halve a year after installing bookworm from scratch on a lime2 board, is is still rock-solid. Even better, homeassistant-supervised is stable and the regular updates install without any issues. If someone is interesed in the installation process for homeassistant, just drop me a personal message

You're certainly right on your device (A20-OLinuXino-LIME2?), and I would love to be able to use the regular debian installer as you do: much more installation options (like full-disk encryption), much more frequent kernel security updates etc

But stock debian is not working on the devices I have.
I have several A20-OLinuXino-MICRO, where I was happily using the regular debian until buster. But, since Bullseye, there are kernel panics that make it unsusable, see my blog post in 2022: https://blog.mossroy.fr/2022/03/31/upgrade-vers-bullseye-des-serveurs-olinuxino/

I also have several A64-OLinuXino-2Ge8G-IND, on which I never could install the regular debian.

I re-tested with debian bookworm in November 2023:
On A20-OLinuXino-MICRO board, the installation worked fine but, after logging in, and using the board a few minutes, there was this kernel panic:

Code Select Expand

[  855.175881] 8<--- cut here ---
[  855.179204] Unable to handle kernel paging request at virtual address fffffffe
[  855.186510] [fffffffe] *pgd=80000040207003, *pmd=6ffce003, *pte=00000000
[  855.193343] Internal error: Oops: 80000207 [#1] SMP ARM
[  855.198608] Modules linked in: binfmt_misc ecb des_generic aes_arm_bs crypto_simd cryptd sun4i_backend axp20x_battery axp20x_adc axp20x_ac_power lima axp20x_pek at24 gpu_sched drm_shmem_helper sun4i_codec snd_soc_core ftdi_sio sun4i_ts snd_pcm_dmaengine nvmem_sunxi_sid snd_pcm usbserial snd_timer snd soundcore sunxi_cedrus(C) sunxi_wdt v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common sun4i_drm_hdmi cec sun4i_ss videodev rc_core libdes mc display_connector leds_gpio cpufreq_dt evdev loop fuse dm_mod configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic axp20x_usb_power industrialio axp20x_regulator pinctrl_axp209 sunxi phy_generic ahci_sunxi dwmac_sunxi stmmac_platform stmmac pcs_xpcs phylink of_mdio fixed_phy fwnode_mdio libphy musb_hdrc libahci_platform libahci i2c_mv64xxx libata sun4i_lradc_keys ohci_platform scsi_mod ohci_hcd udc_core ehci_platform ehci_hcd scsi_common phy_sun4i_usb usbcore spi_sun4i sunxi_mmc sun4i_drm
[  855.199059]  sun4i_frontend sun4i_tcon sun8i_tcon_top drm_dma_helper drm_kms_helper drm
[  855.293448] CPU: 0 PID: 2719 Comm: dpkg-deb Tainted: G         C         6.1.0-12-armmp-lpae #1  Debian 6.1.52-1
[  855.303621] Hardware name: Allwinner sun7i (A20) Family
[  855.308843] PC is at 0xfffffffe
[  855.312001] LR is at free_pipe_info+0x90/0xc4
[  855.316375] pc : [<fffffffe>]    lr : [<c06f260c>]    psr: a0080033
[  855.322637] sp : f0d5def8  ip : 00000010  fp : b6e66368
[  855.327859] r10: 000000f8  r9 : 00000000  r8 : c87f1c38
[  855.333080] r7 : 00000000  r6 : 0000000e  r5 : 00000150  r4 : c3930800
[  855.339601] r3 : ffffffff  r2 : e08db1e0  r1 : c23eed38  r0 : c3930800
[  855.346124] Flags: NzCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment user
[  855.353429] Control: 30c5387d  Table: 43ce01c0  DAC: fffffffd
[  855.359169] Register r0 information: slab kmalloc-cg-128 start c3930800 pointer offset 0 size 128
[  855.368065] Register r1 information: slab kmalloc-cg-512 start c23eec00 pointer offset 312 size 512
[  855.377122] Register r2 information: non-slab/vmalloc memory
[  855.382785] Register r3 information: non-paged memory
[  855.387837] Register r4 information: slab kmalloc-cg-128 start c3930800 pointer offset 0 size 128
[  855.396719] Register r5 information: non-paged memory
[  855.401770] Register r6 information: non-paged memory
[  855.406820] Register r7 information: NULL pointer
[  855.411523] Register r8 information: slab dentry start c87f1c38 pointer offset 0 size 36
[  855.419624] Register r9 information: NULL pointer
[  855.424327] Register r10 information: non-paged memory
[  855.429464] Register r11 information: non-paged memory
[  855.434600] Register r12 information: zero-size pointer
[  855.439823] Process dpkg-deb (pid: 2719, stack limit = 0x2b4da20b)
[  855.446008] Stack: (0xf0d5def8 to 0xf0d5e000)
[  855.450366] dee0:                                                       c3930800 c212b900
[  855.458539] df00: c358b440 c21d19d0 c87f1c38 c06f2760 c212b900 002c0002 c358b440 c06e8f00
[  855.466713] df20: c0450b80 c3aed500 c22bdcc0 000000f8 b6e66368 c93fa840 c26ea8f4 c26ea100
[  855.474886] df40: 00000824 f0d5df70 00000000 c046e1bc c26ea100 c39d5c00 c26ea920 c39d5c38
[  855.483058] df60: f0d5df70 c0450b94 f0d5dfb0 b6e90c04 c1612d98 c0451438 00000000 c3a7b300
[  855.491232] df80: c26ea100 42654441 c04002e4 c9fd1500 b6e66368 c04513f8 000000f8 c045145c
[  855.499403] dfa0: 00000001 c04000c0 00000001 b6e63888 00000000 b6f9e220 00000000 00000000
[  855.507575] dfc0: 00000001 b6e63888 00000000 000000f8 b6e65000 b6e66368 b6e66368 b6e66368
[  855.515749] dfe0: 000000f8 beddba44 b6de2129 b6d77616 60080030 00000000 00000000 00000000
[  855.523935]  free_pipe_info from pipe_release+0xbc/0xc4
[  855.529182]  pipe_release from __fput+0x8c/0x270
[  855.533821]  __fput from task_work_run+0x94/0xc4
[  855.538457]  task_work_run from do_exit+0x30c/0x99c
[  855.543351]  do_exit from do_group_exit+0x40/0x8c
[  855.548071]  do_group_exit from __wake_up_parent+0x0/0x20
[  855.553490] Code: bad PC value
[  855.556668] ---[ end trace 0000000000000000 ]---
[  855.561385] Fixing recursive fault but reboot is needed!
On A64-OLinuXino-2Ge8G-IND, the installation itself worked fine too, but the first boot never reaches the login phase. The console just remains black

#8

ESP32 / ESP32 poe noise

Last post by korneo - May 10, 2024, 03:32:08 PM

Hello everyone,

i have a ESP32-POE2 board and I am reading an potentiometer (0-3.3V) value, however there is a(200KHz) ripple on all voltage rails which is not desirable for accurate measurements.

i have already added an 10nF capacitor close to the input, and a bigger one, which does not help unfortunately.

this significant ripple only appears when the poe power supply is connected(HP1820 J9982A), on usb it works fine and all voltage rails are stable(no 200KHz noise)

does anyone know how i can get rid of the ripple and can obtain a stable adc readout?

thanks in advance

#9

A20 / Re: LIME2 Rev.L lock-up freeze...

Last post by LubOlimex - May 10, 2024, 08:14:47 AM

But what does it say at start of boot over the serial? It is important that the revision is properly listed as revision L. Often people would delete the contents of the EEPROM (thus disabling automatic board recognition by the Olimage) and then also fail to manually configure the board via the u-boot-tools and then the board would load some generic revision A preset that might have settings incompatible with the actual board revision used. Like RAM timings, different LAN controller and so.

#10

A20 / Re: LIME2 Rev.L lock-up freeze...

Last post by mbosschaert - May 09, 2024, 10:29:18 PM

CPU:   Allwinner A20 (SUN7I)
ID:    A20-OLinuXino-LIME2 Rev.L

It identifies like this:

Code Select Expand

CPU: ARMv7 Processor [410fc074] revision 4 (ARMv7), cr=10c5387d
OF: fdt: Machine model: Olimex A20-OLinuXino-LIME2
I'm running an up to date olimex debian bullseye