Found this at my school's electronic garbage bin. As far as I'm aware this is something like an industrial microcontroller. I've put in it 24v that's written next to the only place that looked like it would be happy with me pumping 24v through it and it lit up. I also tried to measure some of the pin outs and yeah they do something.

I would've measured it with an oscilloscope but my dad broke it by probing the motherboard while trying to figure out some anomaly.

Certain PIC MCUs (e.g., pic16f13145 family) have FPGA-like programmable logic called Configurable Logic Block.

The pic16f13115 I'm using has 32 cells each with a 4-input lookup table and a D flip-flop.

To learn to use the tools, today I implemented and simulated support for Charlieplexing of 6 LEDs with PWM brightness control. I used Verilog to define the circuit instead of using the logic CAD canvas.

I was pounding my head on the wall for about half my time. Slowly, I got the Verilog right, got it to synthesize (build), then got it simulating.

It is cool that the CLB programmed logic works even when the CPU is sleeping. It's perfect for safety-critical applications. Can be used, for example, to implement complex interrupt trigger logic. There is great flexibility in hooking up CLB logic to peripheral inputs and outputs. It's much more flexible than the clunkier CLC programmable logic that's been a fixture of PICs.

Just thought I'd share my Eureka experience.

What's the reason for a watchdog taking 23 times as long to reset the device? It turns out the Flash Option Bytes are. And a mass erase doesn't reset those.

Hi everyone,

After a year of reverse-engineering the Thrustmaster T248, I finally have a working wheel emulator, making it possible to build your own custom steering wheel and connect it directly to the T248 wheelbase.

Using my Raspberry Pi Pico–based emulator, your DIY wheel can now:

• Connect directly to the T248 wheelbase (no extra USB cable to the PC needed)

• Send fully functional buttons, DPAD, and encoder inputs

• Use shift paddles with hardware interrupts

• Display the current encoder layer on a small OLED

The emulator replaces the original wheel PCB, allowing you to design completely custom wheels that fully support button, DPAD, and encoder inputs as well as shift paddles. Display telemetry such as RPM, gear, lap time, etc., is not yet supported, so the OLED will currently only show the encoder layer.

Everything you need to build your own wheel – including emulator code, wiring diagrams,  instructions, and detailed technical documentation of the T248 – is available on GitHub:
https://github.com/Spb2005/Thrustmaster-T248-reverse-engineering

Happy building! I’d love to see what kinds of custom wheels the community comes up with.

The wheel shown is a modified Turn Vantage GTE DIY wheel from Turn Racing, adapted for this project.

Hi I was wondering if anyone has done a project using a STM32H743 and something like https://github.com/Infineon/AIROC-Wi-Fi-Bluetooth-STM32

I'd be keen to try it in an LED with mmwave sensor project and was wondering if a dev board exists with wifi on board?

I'm building a project with 2 64x32 hub75 panels working on a matrix portal s3. As of right now I have them both powered by the screw terminals on the board. When plugged in on my PC everything works great! But when I plug it into a wall outlet or battery pack things hit a hitch. It will power on the circuitpy logo and display number of images, then just hang there:

If I restart it or unplug and plug it in a few times it can eventually get to displaying the animations it's loaded with. Sometimes it's hang on second one of these loading screens.

Using a usb power meter, plugged in on the pc it's using 4.83V, 0.33A, 1.64W

On non working power its: 5.97V, 0.44A, 2.20W

If I get it working on a battery it's back to the lower stats

I'd understand needing to power the leds separately if it didn't work at all, but why would it work perfect on my PC and intermittent on battery? I've tried several different wall plugs, battery packs, and PCs and they all react the same way. PCs fine, battery and wall not.

I got some luck by reducing the bit_depth from 6 to 2, but still little luck.

Edit to add: I have tried it with the panels on their own power, no change in behavior. whether sharing the same power bank or two separate ones.

Edit: Resolved! Turned out to be a timing issue. Adding delays on startup and between image loads got it working.

I have a boe-bot kit I want to program in c does anyone know if there's a dev board with the stamps pinout?

Is there a way I can recycle it out of a device?

I have this microcontroller and don't know what to do with this.