Index

MicroWorks 30B4 board

  1. Datasheets 30B4
    1. STM32F103
      1. ADC
      2. STM32 EEPROM
    2. MPU6050
      1. DMA
      2. Issue communications
        1. 01
    3. MPU6050 freq
  2. firmware motor control
  3. Implementations with MicroWorks 30B4 board
  4. Links to sellers

MicroWorks 500W 30km/h motor

  1. BEMF measurements

Flash and Debug STM32

  1. Eclipse IDE and JTAG
  2. Unlock STM32F103 with JTAG
  3. Flash firmware using Bluetooth
    1. STM32F103C6T8 bootloader
    2. ZS-040 Bluetooth module
      1. HC-06 hc01.comV2.0
  4. Serial Port Bluetooth
  5. Serial Port Plot
  6. SM32F103C8T6 use 128kbytes flash

FOC

  1. Observer
  2. Shane Colton documentation and firmware
    1. Firmware
    2. Part 1: Field-Oriented
    3. Part 2: Field-Oriented
    4. Sensorless Pneu Scooter - part 1
    5. Sensorless Pneu Scooter - part 2
    6. Sensorless Pneu Scooter - part 3
  3. Texas Instruments videos
  4. Chinese controllers code

Balance controller

  1. Chinese balance group reference design
  2. Kerry D. Wong -- A Self-Balancing Robot
    1. A Self-Balancing Robot – I
    2. A Self-Balancing Robot – II
    3. A Self-Balancing Robot – III
  3. Self balance bicycle
  4. PID
  5. LQR
    1. Stages of development of the robot-balancer
  6. PID and LQR, MATLAB
  7. Steve Brunton videos

Mechanical parts

  1. Pedals

Various

  1. C language for critical systems
  2. Hall effect sensor placement
  3. The brilliant idea of slow rotating motors
    1. Why does the Torquemax rotate so slowly and so forcefully
  4. Finding Motor Phase-Sensor Combinations

Clipping

  1. Hackaday - 2017.05.07 - opensource firmware for hoverboards

SM32F103C8T6 use 128kbytes flash

On Tue, Feb 05, 2013 at 04:42:53PM +0000, gerrit@... wrote:
> It has been seen on some stm32 targets that the flash size register that
> is probed by the driver may contain an invalid size.

Not only that, I've been told at ##stm32 that all of the STM32F103C8T6
(e.g. as found on ST-Links) have 128K flash instead of 64K. So it's
technically valid but limited for marketing reasons at least on some
chips, here's when this change will come useful too :)
---

Error when trying to flash a file over 64kbytes:
images/1-1.png

After changing this line on the STM32Fxx OpenOCD script file: flash bank $_FLASHNAME stm32f1x 0x0800000 0 0 0 $_TARGETNAME
to: flash bank $_FLASHNAME stm32f1x 0 0x20000 0 0 $_TARGETNAME

Now flashing file over 64kbytes!!! And it works :-)
images/1-2.png