search

shanteacontrols / OpenDeck

Software and hardware platform for simpler building of MIDI controllers.
https://shanteacontrols.com
Apache License 2.0
618 stars 53 forks source link

STM32F4 Discovery #137

Closed Wapata closed 2 years ago

Wapata commented 2 years ago

Hi ! I did put the discovery.bin file into my (new) STM32F4 Discovery, seen the blinking LED, unplugged my MINI-USB, linked PA9 to 5V, plugged the MICRO-USB and then... nothing. No device into windows, into my midi software or into the configuration page.

DETAILS.TXT say that : Version: 0221 Build: Nov 19 2015 15:23:07

Do you have an idea of what could be wrong ? Thanks !

EDIT: it blink FOUR time and not THREE as written.

Wapata commented 2 years ago

The midi IN/OUT din are not mandatory I think. It's should appear as a midi native device and AFTER i can activate midi-din stuff...right ?

paradajz commented 2 years ago

Which F4 Discovery exactly do you have?

Wapata commented 2 years ago

Thanks for the answer.

Front of paper part number STM32F4DISCOVERY from www.st.com/stm32f4-discovery back of the paper 32F407GDISEM/ 01-0 order code STM32F407G-DISC1

On pcb STM32F407G-DISC1 MB997D Label in back of pcb MB997 D-01 2171u0476

... bouth from Farnel in 2017. Don't know if you need something else ? Oh... USB cable checked and okay (two mini and two micro)

paradajz commented 2 years ago

I've just done exactly what the guide says - copied the bin file, waited few seconds, the board rebooted and new MIDI device appeared. Did you try with both mini and micro USB cables connected?

Wapata commented 2 years ago

Never both at the same time. Should I ?

paradajz commented 2 years ago

Yes, please do.

Wapata commented 2 years ago

Nope. 4 flash and then nothing. Jumpers on JP1, DISCOVERY (both), JP2 and JP3 (so on everything)

EDIT : with the STM32 utility i have updated the firmware from V2.J25.M14 to V2.J28.M18 Same behaviour

paradajz commented 2 years ago

Don't know then, really. I have two of those boards here and both work fine. Which OS are you using?

Edit: Ah it's Windows. So nothing at all shows up in Device Manager?

Wapata commented 2 years ago

Yes it's windows. I will try with Linux at the end of the week then. (All my custom midi devices work great on my computer). I don't find what 3 or 4 flash mean by the way .. Thanks for your help !

Wapata commented 2 years ago

I've read that some time Github corrupt individual files but it's okay if we download the whole project. But... it doesn't work as i don't find the file inside the ZIP.

Could you please send me a mail with discovery.bin in it ? wapata.31@gmail.com if possible.

Wapata commented 2 years ago

In linux it failed too BUT a file is disposed into the device. FAIL.TXT say: The interface firmware FAILED to initialize the target MCU

Wapata commented 2 years ago

Okay... trying an other pair of cables and it work :'-( ... I have to found the instructable that show ow to make a USB cable health check.

I am SO sorry about that. I have to put labels on theses "bad data / power ok" cable :-(

paradajz commented 2 years ago

This might be for you: https://www.tindie.com/products/nerfhammer/is-it-me-or-is-it-usb/