View allAll Photos Tagged STM32
To better understand the STM32H747, I purchased this development board. It uses the same dual core chip as the Arduino Giga R1. The development tool used is the STM32CubeIDE. With this tool, you can easily configure your application and just need to add your own additional program part. The tool has a full graphical configuration interface. Lots of examples are available.
My desk and my current projects (as seen in the video I made for a video for the Hackaday Prize about working from home).
Projects: ArduTouch synthesizer kit (Arduino), ArduTouch synthesizer V2 (Raspberry Pi Pico), Automatic weighing of re-usable food container AI (Raspberry Pi), Re-usable-food container collection box (ESP32), mischievous ultra-sonic speaker (STM32), laser-pointer gloves (ATtiny2313), Gumball Sound Capsule cat toy (ATtiny13), soldering workshop setup (with OBS, microphone, and 3 cameras).
Berlin
June-2021
Part of a winter project to adapt an 1980s Amstrad Computer joystick to work with a modern PC, or Andriod Phone. Project uses the STM32 (STM32F103C8T6) Board, this board appears as USB Game PAD HID.
Top side of the StarPointer virtual electronic finderscope.
All the details of this project are available at jayakody2000lk.blogspot.com/2022/06/virtual-electronic-fi...
Bottom side of the StarPointer virtual electronic finderscope.
All the details of this project are available at jayakody2000lk.blogspot.com/2022/06/virtual-electronic-fi...
Part of a winter project to adapt an 1980s Amstrad Computer joystick to work with a modern PC, or Andriod Phone. Project uses the STM32 (STM32F103C8T6) Board, this board appears as USB Game PAD HID.
A basic STM32 breakout board that exposes several I2C, SPI, USART etc interfaces as well as a simplified JTAG interface and several power pins. A miniUSB plug is connected to the STM32's USB peripheral and two LEDs sit on timer channels. The switches are power on/off and boot selection: bootloader or user code.
A basic STM32 breakout board that exposes several I2C, SPI, USART etc interfaces as well as a simplified JTAG interface and several power pins. A miniUSB plug is connected to the STM32's USB peripheral and two LEDs sit on timer channels. The switches are power on/off and boot selection: bootloader or user code.
Robot3 has an IR rangefinder, one of my STM32 development boards and an xbee radio running the new ZB firmware. There's also a small motor controller board hidden inside the old battery compartment as well as a 900mAh lipo. The rear two wheels are driven by one motor which is speed controlled by a PWM output from the STM32, while the front two have another motor on a rack and pinion that steers them and is driven by a simple high or low signal from the STM32.
The car can be manually remote controlled over the xbee wireless link but automatically backs away from detected obstacles. Alternatively it can simply drive forwards until it detects an obstacle, then reverse away.
Development slowed once I got the parts for the somewhat more interesting quadcopter UAV.
A basic STM32 breakout board that exposes several I2C, SPI, USART etc interfaces as well as a simplified JTAG interface and several power pins. A miniUSB plug is connected to the STM32's USB peripheral and two LEDs sit on timer channels. The switches are power on/off and boot selection: bootloader or user code.
A basic STM32 breakout board that exposes several I2C, SPI, USART etc interfaces as well as a simplified JTAG interface and several power pins. A miniUSB plug is connected to the STM32's USB peripheral and two LEDs sit on timer channels. The switches are power on/off and boot selection: bootloader or user code.
This is the STM32 OnStep Controller PCB. The microUSB connection, ST4 and two axes are on the right. The power connection on the left. The power connection, and the cardboard box as a case are temporary as prototypes for the mean time.
It took *ages* to get this thing working. It took a while to find the programmer, then to compile the programmer, then to figure out how to use the programmer. Then to find the compiler, then to get it to compile the code. Then to upload the code.
Then to edit the code to get it working on the internal clock. Eventually (some weeks after making the board), it can flash an LED! The possibilities are endless.
The new driver circuit boards are assembled and ready for testing. Perhaps this evening the control software can speak to it for the first time.
Testing an MPU6050. Not generating fancy patterns yet, just indicating acceleration (RGB) and angular rate (CMY) on the LED-strip.
espitek.com/arduino/lap-trinh-stm32-voi-arduino-ide/
espitek.com/arduino/arduino-la-gi/
espitek.com/arduino/thung-rac-tu-dong-huong-dan-tu-che-su...
espitek.com/arduino/nap-code-tu-xa-cho-arduino-khong-can-...
espitek.com/arduino/huong-dan-lam-xe-leo-tuong-dieu-khien...
espitek.com/arduino/dieu-khien-dong-co-buoc-dung-arduino-...
espitek.com/cong-nghe/guong-thong-minh-cong-nghe-cho-tuon...
Top view of the USB seven segment display module PCB.
This is the final prototype board of the display module which is described in github.com/dilshan/usb-external-display.
Disassembled a Liveview (MN800), here is one side of the main PCB.
This design seems to be centered around a ST flip chip (U3), probably an STM32. The exact part marking is: "32F103C6" "8N KP9 93" "SGP 045 Z" "(ST logo) (E1 symbol)"
Chip by the antenna (seems to be "U1") is "2584A0" "AA037" "(E1 symbol) 103" "VQ TWN"
Weeks of slogging through as much documentation and examples as I could find and I've managed to make a bare-bones build environment for this chip as well as the toolchain needed to compile and program it. A short while later, I've got USART1 working successfully to send info to this OLED screen (at 300 baud, shh). No luck getting USART3 to work with it, I'll try that next.
Still, success!
Got both chips soldered! One is an STM32 F103 chip which I hope to use, the other is an ST710 thing which is a bit smaller and less interesting but cheaper and easier to solder. Both were a bit of a pain though - pretty tiny! The largest chip is about half the size of my thumbnail.
Robot3 has an IR rangefinder, one of my STM32 development boards and an xbee radio running the new ZB firmware. There's also a small motor controller board hidden inside the old battery compartment as well as a 900mAh lipo. The rear two wheels are driven by one motor which is speed controlled by a PWM output from the STM32, while the front two have another motor on a rack and pinion that steers them and is driven by a simple high or low signal from the STM32.
The car can be manually remote controlled over the xbee wireless link but automatically backs away from detected obstacles. Alternatively it can simply drive forwards until it detects an obstacle, then reverse away.
Development slowed once I got the parts for the somewhat more interesting quadcopter UAV.
Weeks of slogging through as much documentation and examples as I could find and I've managed to make a bare-bones build environment for this chip as well as the toolchain needed to compile and program it. A short while later, I've got USART1 working successfully to send info to this OLED screen (at 300 baud, shh). No luck getting USART3 to work with it, I'll try that next.
Still, success!
Weeks of slogging through as much documentation and examples as I could find and I've managed to make a bare-bones build environment for this chip as well as the toolchain needed to compile and program it. A short while later, I've got USART1 working successfully to send info to this OLED screen (at 300 baud, shh). No luck getting USART3 to work with it, I'll try that next.
Still, success!
Got both chips soldered! One is an STM32 F103 chip which I hope to use, the other is an ST710 thing which is a bit smaller and less interesting but cheaper and easier to solder. Both were a bit of a pain though - pretty tiny! The largest chip is about half the size of my thumbnail.
Robot3 has an IR rangefinder, one of my STM32 development boards and an xbee radio running the new ZB firmware. There's also a small motor controller board hidden inside the old battery compartment as well as a 900mAh lipo. The rear two wheels are driven by one motor which is speed controlled by a PWM output from the STM32, while the front two have another motor on a rack and pinion that steers them and is driven by a simple high or low signal from the STM32.
The car can be manually remote controlled over the xbee wireless link but automatically backs away from detected obstacles. Alternatively it can simply drive forwards until it detects an obstacle, then reverse away.
Development slowed once I got the parts for the somewhat more interesting quadcopter UAV.
This is the complete setup. It is a C8 with a 0.63X reducer, so effective focal length is ~ 1310 mm F/6.3. Canon T4i, heated dew shield. All of this on a Vixen SXD mount that had its servo motors replaced with Vexta NEMA11 steppers with an 18:1 gear head. The electronics were replaced with STM32 OnStep.
For more on OnStep STM32 go here
Got both chips soldered! One is an STM32 F103 chip which I hope to use, the other is an ST710 thing which is a bit smaller and less interesting but cheaper and easier to solder. Both were a bit of a pain though - pretty tiny! The largest chip is about half the size of my thumbnail.
A small perfboard is used with RJ45 breakout boards to connect the controller to the motors, using these off the shelf Ethernet cables. The empty space on the right will have connections for PEC Sense and Polar Scope reticle.
Robot3 has an IR rangefinder, one of my STM32 development boards and an xbee radio running the new ZB firmware. There's also a small motor controller board hidden inside the old battery compartment as well as a 900mAh lipo. The rear two wheels are driven by one motor which is speed controlled by a PWM output from the STM32, while the front two have another motor on a rack and pinion that steers them and is driven by a simple high or low signal from the STM32.
The car can be manually remote controlled over the xbee wireless link but automatically backs away from detected obstacles. Alternatively it can simply drive forwards until it detects an obstacle, then reverse away.
Development slowed once I got the parts for the somewhat more interesting quadcopter UAV.
Got both chips soldered! One is an STM32 F103 chip which I hope to use, the other is an ST710 thing which is a bit smaller and less interesting but cheaper and easier to solder. Both were a bit of a pain though - pretty tiny! The largest chip is about half the size of my thumbnail.
I did kind of a lazy job on these setup shots, and wish they were better, but I wanted to post something about the setup. This is the behind the scenes electronics. I'm using an STM32 microcontroller to drive the timing, and the custom protoboad is just some MOSFETs and connectors to drive the output signals to the valve, camera, and flash. I've written the software so that an application on the laptop defines and triggers the firing sequence, so it is quick to edit delays, valve open times, etc. Also, I've been tethering my D90 using DCamCapture so that the photos are downloaded for preview right away. A 12V lead acid battery is used to power the solenoid valve.
This is a temporary power socket. Standard 2.1/5.5mm barrel jack. An off the shelf 12V 2A power supply is enough for the dew heater and OnStep
This is how the new stepper motors were mounted, to replace the servo motors. Two 16 tooth pulleys for a 1:1 ratio, since the Vexta NEMA11 motors have an 18:1 gear head which is sufficient gear reduction. One screw goes into the hole in a corner, and anther new hole was drilled and made a bit wider than the screw. This allowed the belt to be put then tensioned by pulling the motor away from the other pulley, then tightening the screw, which has a washer.
This switch is used to put the microcontroller in flash mode, so a new version of OnStep can be uploaded to the controller. It is now in run mode (switch to the right).
Robot3 has an IR rangefinder, one of my STM32 development boards and an xbee radio running the new ZB firmware. There's also a small motor controller board hidden inside the old battery compartment as well as a 900mAh lipo. The rear two wheels are driven by one motor which is speed controlled by a PWM output from the STM32, while the front two have another motor on a rack and pinion that steers them and is driven by a simple high or low signal from the STM32.
The car can be manually remote controlled over the xbee wireless link but automatically backs away from detected obstacles. Alternatively it can simply drive forwards until it detects an obstacle, then reverse away.
Development slowed once I got the parts for the somewhat more interesting quadcopter UAV.
Bottom view of the USB seven segment display module PCB.
This is the final prototype board of the display module which is described in github.com/dilshan/usb-external-display.
A DLP-USB1232H and OpenOCD based JTAG adapter connected to an example board (Olimex STM32-H103).
randomprojects.org/wiki/DLP-USB1232H_and_OpenOCD_based_JT...