Shield is not detected by Raspberry Pi about motor_shield_firmware

[ramboza]

How to solve it ?!

[eddie4]

I didn't I switched to another shield

[fabianoriccardi]

I think there are problem about the fixed packet length. This code seems to wait 4 bytes to continue...
I tried a simple i2c scanner for arduino, and after the first (successfull) scan, the module starts to mess up the entire I2C bus... and of course it can't be reached until reset!

[TungstenE2]

There is a new motor_shield.bin available which fixed I2C issue.

See espeasy plugin wiki.

https://www.letscontrolit.com/wiki/index.php?title=WemosMotorshield

Download the motor_shield.bin:

https://cdn.hackaday.io/files/18439788894176/motor_shield.bin

or

https://github.com/pbugalski/wemos_motor_shield

Download STM32Flash from here https://sourceforge.net/projects/stm32flash/files/

Extract and put the above files into a directory

Plug in your USB serial device and make a note of the COM port it uses

Those of you who want to do this using Window's 8/10:

Window Command Prompt cd to the directory

1. 'stm32flash.exe COM9' replace COM9 with your COM port number

2. 'stm32flash.exe -k COM9' This will unlock your shield

3. 'stm32flash.exe -f -v -w motor_shield.bin COM9' This will flash the bin and re-lock the shield.

WemosMotorshield03.PNG

Then disconnect all the wires (including the RTS pin), connect the shield to your ESP device (eg. WeMos D1 Mini), and it should work.

see also: https://hackaday.io/project/18439-motor-shield-reprogramming

[mortlind]

@TungstenE2 When I have flashed the new firmware, do I then need to desolder any of the I2C and the RST pads?

[TungstenE2]

@TungstenE2 When I have flashed the new firmware, do I then need to desolder any of the I2C and the RST pads?

the was no need for soldering in may case, as far as I remember

[mortlind]

@TungstenE2 So you never soldered any of the pads underneath?