Blog - All Comments

RE: E-Z USB to I2C Adapter and UART Bridge

genebren — Wed, 10 Jun 2026 22:59:29 GMT

Very cool! I have had some projects where that feature set might have been useful.

A bit of topic, but I have dealt with limited comm ports in several projects (specifically working with laboratory equipment, like pumps and sensors) where I needed more pumps. At one point I developed a comm port multiplexer, where a single comm port connected to a ATmega device could drive multiple slave boards with 2 comm ports. I built and sold several of these devices, along with a comm library to allow the slave ports to appear as actual comm port. This was more than 20 years ago. There are far more capable devices available today.

RE: E-Z USB to I2C Adapter and UART Bridge

DAB — Tue, 09 Jun 2026 19:30:00 GMT

Nice post.

This device could be very useful.

RE: Solving Error: Unknown flash device: An OpenOCD Upgrade for Pi Pico / Xiao and other RP2040 Boards

Coconut1 — Sat, 14 Feb 2026 20:56:10 GMT

I had the exact same problem as described above. Bought 4 cheap Pico Boards online and encountered the connection problem when starting to debug.
With a closer look at the board I could see that there is no 10-pin voltage regulator but a unknown 6-pin and additionally a 2MB Flash 'BY25Q16ES' from
the chines manufacture BYTe Semiconductor. So I was sure, these boards where counterfeit PICOs.
The error message then was
--> Error: Unknown flash device (ID 0x00154068)

The by far easiest way to solve this, is to open the openocd.exe in a text editor and search for the entries of the table shown above.
The 10 values of each line there will be interpreted as:
name, read_cmd, qread_cmd, pprog_cmd, erase_cmd, chip_erase_cmd, device_id, pagesize, sectorsize, size_in_bytes

Now since I knew my Flash device, I download its data sheet and checked for the read/write/prog/erase commands and found that there already is an almost identical device
given with a slightly different device ID 0x001540C8. The rest was easy.
Seraching in a text editor (e.g. np++ in HEX-mode) for the byte-sequence "C8 40 15 00" and finding a "03 00 02 D8 C7 00 00 00" next to it, indicating the correct file position.
Now I changed the "C8" to "68" and saved the modified file openocd.exe.

And it worked!!! The debugger now starts smoothly and every thing is fine ... now after 30+ hours of serching and trying.

RE: Solving Error: Unknown flash device: An OpenOCD Upgrade for Pi Pico / Xiao and other RP2040 Boards

Coconut1 — Sat, 14 Feb 2026 20:44:54 GMT

The by far easiest way to solve this, is to open the openocd.exe in a text editor and search for the entries of the table shown above.
The 10 values of each line there will be interpreted as:
name, read_cmd, qread_cmd, pprog_cmd, erase_cmd, chip_erase_cmd, device_id, pagesize, sectorsize, size_in_bytes

Now since I knew my Flash device I download its data sheet and checked for the read/write/prog/erase commands and found that there already is an almost identical device
"st m25pe16" given with a slightly different device ID 0x00158020.
The rest was easy. Seraching in a text editor (e.g. np++ in HEX-mode) for the byte-sequence “20 80 15 00” and finding a “03 00 02 D8 C7 00 00 00” next to it, indicating the correct file position. Now I changed the "20 80" to 68 40" and saved the modified file.

And viola … it worked. The debugger now started smoothly. Every thing is fine now … after 50+ hours of serching and trying.

RE: Syslog: Sending Log Messages to a Server with MicroPython

DAB — Fri, 30 Jan 2026 20:30:50 GMT

Great post.

RE: Adafruit Pi Pico Enclosure: A Quick Review

DAB — Fri, 30 Jan 2026 20:20:08 GMT

Interesting, thanks for the review.

RE: Adafruit Pi Pico Enclosure: A Quick Review

genebren — Thu, 29 Jan 2026 17:13:30 GMT

But don't forget that this cute little thing could be strapped to your wrist for the ultimate computing to go experience [emoticon:44a8a53ad3364ea78a16c5a3229f75bb]

RE: Adafruit Pi Pico Enclosure: A Quick Review

dougw — Thu, 29 Jan 2026 15:50:30 GMT

The primary usage would seem to be as a case that allows Pico modules to be stored & programmed without touching the actual CCA - reduced ESD risk during some small part of the workflow?

RE: Adafruit Pi Pico Enclosure: A Quick Review

balajivan1995 — Thu, 29 Jan 2026 04:38:04 GMT

Reminds me of people putting back case on iPhones that covers everything except the Apple logo.

RE: Adafruit Pi Pico Enclosure: A Quick Review

robogary — Thu, 29 Jan 2026 00:27:35 GMT

A squirt of hot glue or a scrap of foam would hold it in place. Doesnt seem to be useful except to keep someone's bearded dragon from eating it

RE: Syslog: Sending Log Messages to a Server with MicroPython

balajivan1995 — Mon, 26 Jan 2026 11:08:23 GMT

I have once used plain UDP multicast to send data from one esp32 to another. If the temperature doesn't change drastically, you can use plain UDP to send message and receive it using Wireshark. It won't take much time to transmit a message, payload is much smaller.

RE: Syslog: Sending Log Messages to a Server with MicroPython

embeddedguy — Mon, 26 Jan 2026 05:39:39 GMT

Nice first line, I fell the same. about Micropython.

RE: Syslog: Sending Log Messages to a Server with MicroPython

BigG — Sun, 25 Jan 2026 18:26:07 GMT

"Installing MicroPython on your microcontroller board allows you to write and immediately run Python code, without needing to build or compile the code. It’s a really fast way of creating applications."

Interesting perspective... surely that's fast (and loose). I would add that this is best served in a class room environment, with a note on the wall... please leave all (micro)Python behind when leaving.

Besides that, this is a nice logging method.

RE: Syslog: Sending Log Messages to a Server with MicroPython

veluv01 — Sun, 25 Jan 2026 17:45:31 GMT

Interesting application!

RE: Create a BLE 3D orientation sensing device using Raspberry Pi Pico 2 W (with C SDK) and 6DoF sensor

Jan Cumps — Sun, 09 Nov 2025 13:22:40 GMT

I tried the BLE Temperature Sensor example today, on a Pico2 W. Just to get a feeling for how that part of the SDK works. The same exercise as you describe above. I used the RISCV, to have at least one difference [emoticon:c4563cd7d5574777a71c318021cbbcc8]

As client, I used an Android phone, and Infineon's BLE app

I asked ChatGPT what the 0xeb08 means in BLE lingo:

Not bad! It's in line with the debug log of the Pico:

The 24.23 answer from ChatGPT is because I asked this for two captured hex values

I haven't tried custom services yet.