Baite STLINKV2 -> Baite MM

Does anyone have the Baite MM pins that match the ones in this doc?

https://github.com/rogerclarkmelbourne/ … from-Linux

They don’t have the header and I Cant; see anything on the silkscreen that matches, even better, is there a guide like above but for the BMM?

My MM does the normal flash (fast – slow) routine but no longer shows as DFU nor Serial on my Mac, not sure what I did, I might have pulled the plug mid flash or something, so need to get it back.

Nevermind, my brain too stupid atm to search for maple mini pinout.

https://developer.mbed.org/media/upload … nout01.png

*sigh*

Has anyone had any joy using OpenOCD on OSX with a MM? Following https://github.com/rogerclarkmelbourne/ … from-Linux I just get

Error: Debug adapter does not support any transports? Check config file order.
Error: unable to select a session transport. Can't continue.

HexTank wrote:
Unfortunately, whilst I have the flashes on reset, holding but=32 doesn’t lock in to dry mode, however, using st-utils from texane which connects to the board, but, arm-none-eabi-gdb requires an elf rather than bin so unable to upload the boot loader that way.

Thank Roger, I’ll give that a try. I noticed there was a st-flash exe that comes with the st-utils which I assumed was for flashing the stlink itself but reading various things last night it seemed it was used when using an STlink to turn another STlink in to a BMP so may be that’s an actual flasher I could try.

It’s annoying that I have to fire st-link at least when the blue flashes happen on a reset else it won’t connect so might need hands all over the place and obviously if a fail the burn and lose the flashes it’s pretty much dead.

HexTank wrote:It’s annoying that I have to fire st-link at least when the blue flashes happen on a reset else it won’t connect so might need hands all over the place and obviously if a fail the burn and lose the flashes it’s pretty much dead.

I’m suprised I didn’t already join the club on first usage as I have one of the green stlinkv2s which has no pinouts on the casing, so I hooked it up based on the pinouts based on the blue casing, which are completely different, dodged the bullet thusfar.

I agree with Andy

I have done various things that should have fried the STM32, but they all survived so far.

I ran one board from 5V instead of 3.3, for several days, and it didn’t seem to do it any long term harm.

SHE LIVES!!!!! thanks chaps, learnt a few things on the way.

1) ST-* for osx is included in the git archive so no need for home-brew.
2) Don’t get side tracked using dfu-util manually when it’ll just work like magic from Arduino IDE anyway once the bootloader is sorted.

I managed to get it working using the following (should anyone bother with OpenOCD/st-util/gdb or variants and have no luck)

st-flash erase
st-flash –reset <your_bootloader_of_choice> 0x08000000

I assume the address for the boot loader is correct as I can get a simple flash sketch running, now to find why my sketch crashes.. goto 10

Cheers guys.

I had no joy with boot20 though, dfe-util complaining about something (which I’ll grab when I try again )

*EDIT: found my bug and what was the probable cause of it all, having a big enough array that the stack will get trashed from the off.

LOL

Things are easy when you know how to do them