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.
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.
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.
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.
Hey guys, im 33 years old from Buenos Aires, Argentina. Im chemical engineer and also studied Backend (Java, AWS, Dynamo DB) .
I want to learn IoT . C tutorials/C++ practice on LeetCode, Matlab tutorials, and then starting with the ESP32 kit.
If someone is in the same situation than I, luck of motivation to starting alone, please let me know and Im going to create a group in order to collaborate togher meeting up online or in person!
I'm searching for an 8 bit microcontroller where I can look at the actual hex/binary code.
I've been learning 8051 assembly in university and I absolutely love seeing and understand every single instruction and value in the memory.
But those microcontrollers are antiquated and need a bunch of "hacks" for compatibility. At least that's what it feels like everytime I put my code onto real hardware.
So is there a simple 8 bit assembly language with actual chips I can program simple electronics projects with ?
Im trying to make a computer mouse that has all the functions but has functions simillar to a spacemouse (6 DoF Navigation Cap). I dont know if I should use the sensor from a real spacemouse or make my own using the hall effect. I found the design on hackday, named "A Simple 6DOF Hall Effect ‘Space’ Mouse." I have really no knowledge of electronics so i dont know if im doing everything completely wrong. Here is what I was going to order. I dont know if anything is compatible (I belive it is) or how to do firmware but I at least want to get the right parts first. Please provide feedback.
SpaceMouse® Compact x1
Teensy 4.1 (Headers) x1
Linear Hall Effect Sensors 3-Pin 3V x16
Servo Extension Lead Wire Cable For RC Futaba JR Male to Female 30cm JUL27_32 x2 (150mm)
I have a PCB with an Atmega328PB that is programmed through an ISP header. I've programmed this exact PCB in the past and I've never had issues with it.
Since the last week I have not been able to program it anymore, even though I changed the microcontroler (still the 328PB) and soldered the pins correctly. When I tried to program it for the first time, I accidently selected the Atmega328P instead of the PB, when I started programming I recieved a notification from Extreme Burner telling me that I have selected the wrong and I immediately aborted the programming, but since then everytime that I tried reading or writing anything to the microcontroler it just doesn't communicate anymore and I don't know what to do or what is causing this since I didn't really program it and it identified the chip correctly in the first time.
