May 07, 2024, 07:18:18 PM

Recent posts

#1
UEXT / Re: MOD-RFID1356MIFARE - Attac...
Last post by LubOlimex - Today at 04:35:50 PM
Did you first cut out the on-board antenna?

We haven't tested external antenna ourselves, nor have we provided any instructions how it should be done.

We designed the on-board antenna after public document AN<10447_1> PN532 demoboard - look for the information for PCB1648-1.

Maybe disconnect the on-board antenna and measure how much microhenry it is and see if your external antenna is similar.
#2
A20 / Re: A20-OLinuXino-MICRO + Debi...
Last post by amd - Today at 12:46:21 PM
Quote from: LubOlimex on Today at 08:49:48 AMIt might be hard to get it working. It is made for RPi and their Linux distribution. As it listed at GitHub flutter-pi is only tested on a Rasberry Pi 4 2GB...

It won't work out-of-the-box with any board different than RPi and any distribution different than Raspberry Pi OS. The good news is that Allwinner A20 chip is ARMv7 architecture which is listed as supported by the project. The bad news is I am not sure if the hardware acceleration requirements are met.
According to flutter-pi documentation,

QuoteAlthough flutter-pi is only tested on a Rasberry Pi 4 2GB, it should work fine on other linux platforms, with the following conditions:

  • support for hardware 3D acceleration. more precisely support for kernel-modesetting (KMS) and the direct rendering infrastructure (DRI)
  • CPU architecture is one of ARMv7, ARMv8, x86 or x86 64bit.

Of course, condition #2 is met.

Regarding the first one, I don't know how to get detailed information about what mesa/lima drivers for Mali400 do support and do not support.
Using strace, I managed to verify that flutter-pi quits because of a failing IOCTL that makes use of the DRM_IOCTL_SET_CLIENT_CAP parameter.

Any idea?
   
#3
STMP1 / Re: Olimex STMP1 SOM - Error s...
Last post by LubOlimex - Today at 09:05:15 AM
It sounds like the same issue. You can easily test if it is - try the image without AXP initialization just to confirm. If these five boards that never boot, boot with it, then it is the same issue. Image is here:

https://ftp.olimex.com/TEMP/SOM-NO-AXP209/STM32MP1-OLinuXino-SOM-bullseye-minimal-20240328-133932.img.7z

Contact us at support@olimex.com about the issue with the boards that won't start when power supply is applied.

> Quick power cuts seems to cause the problem every time.

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.
#4
A20 / Re: A20-OLinuXino-MICRO + Debi...
Last post by LubOlimex - Today at 08:49:48 AM
It might be hard to get it working. It is made for RPi and their Linux distribution. As it listed at GitHub flutter-pi is only tested on a Rasberry Pi 4 2GB...

It won't work out-of-the-box with any board different than RPi and any distribution different than Raspberry Pi OS. The good news is that Allwinner A20 chip is ARMv7 architecture which is listed as supported by the project. The bad news is I am not sure if the hardware acceleration requirements are met.
#6
ESP32 / Re: ESP-POE-ISO and TFT_eSPI
Last post by LubOlimex - Today at 08:28:21 AM
Which pins exactly are you using for the LCD?
#7
ESP32 / Re: ESP32-POE: esp_eth_driver_...
Last post by LubOlimex - Today at 08:25:22 AM
2.0.14 and  2.0.16 should require nothing extra. If it doesn't work out-of-the-box with  2.0.14 and  2.0.16 then the problem is with the Arduino package installation (it sometimes bugs out when you switch between newer and older versions of packages), this might require full reinstall or manual deletion.
#8
ESP32 / Re: ESP32-POE: esp_eth_driver_...
Last post by DirkB19 - May 06, 2024, 09:09:08 PM
I just received my OLIMEX ESP32-POE2 board ...
and I have the same problem as mentioned in this post.
20:04:23.112 -> E (4121) lan87xx: lan87xx_pwrctl(409): power up timeout
20:04:23.112 -> E (4121) lan87xx: lan87xx_init(491): power control failed
20:04:23.112 -> E (4121) esp_eth: esp_eth_driver_install(215): init phy failed
Tried different board revisions in Arduino:  2.0.14, 2.0.16, 3.0.0
Tried with and without #defines

What could be wrong ?
Thx
#9
A20 / A20-OLinuXino-MICRO + Debian B...
Last post by amd - May 05, 2024, 08:51:14 PM
Hi,

I'm trying to run a very simple Flutter application that just prints a string on the console. For the sake of simplicity, I'm using flutter-pi tool: https://github.com/ardera/flutter-pi. The application can not run because of the following error:

$ flutter-pi flutter_assets/
modesetting.c: Could not set DRM client universal planes capable. drmSetClientCap: Operation not supported
flutter-pi.c: Could not create drmdev from device at "/dev/dri/card0". Continuing.
flutter-pi.c: flutter-pi couldn't find a usable DRM device.
Please make sure you've enabled the Fake-KMS driver in raspi-config.
If you're not using a Raspberry Pi, please make sure there's KMS support for your graphics chip.

How to set up DRM/KMS properly in order to run this app?

Thank you in advance.
#10
UEXT / MOD-RFID1356MIFARE - Attaching...
Last post by Vicky_winkler - May 05, 2024, 12:45:57 PM
Hi everybody,

We need to attach an external antenna to the MOD-RFID1356MIFARE as the place where the device is supposed to go, is too little for it. We've done some research and could not really find any information on how to do so with the MOD-RFID1356MIFARE. There is a similar question about this here, but it was not helpful. (https://www.olimex.com/forum/index.php?topic=7971.msg30016#msg30016)

So far, we've attached the Antenna using the 3 through-hole pins (AN1, AN2, GND) and it worked just like the built-in one. Unfortunately, though, after some testing the MOD-RFID1356MIFARE started to behave strangely and eventually broke. This could be a coincident as the MOD-RFID1356MIFARE used for testing was a bit older and had signs of wear. However, it might also be that attaching an external antenna requires to add parts onto the unsoldered pads on the MOD-RFID1356MIFARE-PCB.

Therefore, we wanted to ask if someone here has tried this before and has some experience with it or can confirm that this was a pure coincidence before we destroy another device.

The antenna we tried to attach is this one: https://www.digikey.it/it/products/detail/eccel-technology-limited/000333/16840651

Any information is much appreciated.