Search the Community

Hi there, I have no virtualized Windows so I am trying to flash the bootloader with openocd: openocd -f stm32f4discovery.cfg -c "program project.bin exit" I get following output: Open On-Chip Debugger 0.9.0 (2015-11-28-15:54) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD adapter speed: 2000 kHz adapter_nsrst_delay: 100 none separate srst_only separate srst_nogate srst_open_drain connect_deassert_srst Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : Unable to match requested speed 2000 kHz, using 1800 kHz Info : clock speed 1800 kHz Info : STLINK v2 JTAG v14 API v2 SWIM v0 VID 0x0483 PID 0x3748 Info : using stlink api v2 Info : Target voltage: 2.891327 Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints target state: halted target halted due to debug-request, current mode: Thread xPSR: 0x01000000 pc: 0x0800637c msp: 0x20000c78 ** Programming Started ** auto erase enabled Info : device id = 0x10036413 Info : flash size = 1024kbytes Warn : no flash bank found for address 0 wrote 0 bytes from file project.bin in 0.001464s (0.000 KiB/s) ** Programming Finished ** shutdown command invoked I guess I need an offset, but how large? Thanks and best regards, Uli The following seems to work: openocd -f stm32f4discovery.cfg -c "program project.bin exit 0x08000000" At least it doesn't throw an error. But it shows up as "Van Ooijen Technische Informatica". Isn't this weird?

Hello all, I have recently completed a Sammich that has been sitting on a friends shelf for the last 4 years! I will explain what has happened so far to try and give a clear picture. The build went really well apart from a lifted pad which was repaired (this only affected the low power LCD backlight) and is now working. Everything electrical checks out, all test points are clear and there are no shorts, the correct jumpers are set for the 8508 SID's, the voltage jumpers are correct also. Basically the Sammich turns on and the LCD shows some black squares, then tells me: MIOS v1.9g ©2009 T Klose, and then goes on to say READY. I have an M-Audio 2x2 midisport usb interface, I have downloaded the latest MIOS Studio software (PC and Mac), and the latest setup_sammich_sid.hex, and the mios_v1_9g_pic18f4685.hex My problem is that no matter what i do, it doesn't seem to want to let me upload the hex file to the PIC/Sammich. when I first power on the sammich, if i press query in the mios studio immediately, i get the screen telling me its connected to the core and ready, and then i browse for the setup_sammich_sid.hex and hit start, and then it tells me it can't contact the core and to reboot the sammich, which i do, it tries to do it then it says it can't it and gives me an error saying: Upload aborted due to error #12: MIDI IN Frame ErrorNo response from core after 16 retries! It only ever seems to give me the connected to core message immediately after I power it on, and press query, and then only very briefly, from what i understand, it is supposed to keep polling every few seconds for an upload if it doesn't have mios/hex burnt in. I have tried doing this under windows 7 64bit, and OS X 10.10, using the same M-Audio 2x2 ( isee from the white/blacklist that this particular device may not work under OS X, hence why I'm trying under windows 7. I have looked at the troubleshooting guide, and done the midi loopback tests from the PC and the sammich, and the check out fine. I think i either have a duff midi interface, or something else is wrong. I will post some screenshots incase anyone else can help by looking at them, any help is greatly appreciated. [EDIT] I have now tried to upload the file from another 2 different types of midi interface on the Mac, but still have the same error in mios studio. [EDIT] I have just purchased a Neusonik uMIDI/O22 to test with, once it arrives i will give it a go and see if it makes any difference.