Primate

Hi, I'm in the middle of an MIDIBox project and it came to my mind that I could use a I2S compatible audio DAC (TI PCM1754 or PCM1781). I have been reading about the I2S synth on SVN repositories and have some questions: Is it possible to make this pinning: - LRCIN (WS) -> PA15 (J3:TDI) - BCKIN (CK) -> PB3 (J3:TDO) - DIN (SD) -> PB5 (J19:SO) - SCKI (MCLK) -> PC6 (J15B:E) or PC7 (J15A:E) If yes, how should the MIOS32_SRIO_SPI (in the mios32_config.h) be defined since neither SPI0 (J16) and SPI1 (J8) are used? Is it possible to use the DAC to make an audio output for headphones (i.e. while using Traktor)? Best regards

I successfully uploaded the bootloader...BUT via COM port (ROM based UART Bootloader method) :frantics: I wasted three days to get the JTAG going but with no success and I think that the COM port method is the easiest one. First of all less hardware components are required for the job (a COM port connector, four 100nF capacitors and a MAX232). Second and most important the bootloader upload is painless and quick. So all the noobs out there be aware of this. Never the less tnx to everybody who helped to get my Core going...and now for the fun :D Best regards, Primate

I have placed all files (parport_lpt1.cfg, STM32F10x.cfg, STM32F10x_upload.script, project.bin) to C:\Program Files\OpenOCD\0.1.0\bin I have soldered a LED+resistor between Ucc and GND on the wiggler. I power it trough a USB, voltages are 2.9 V, I think that's ok. I'm using a Phillips 74HC244N, it has a little bit different pins then 74AC244 but I have taken that into account. Transistor and resistors are ok. I also doublechecked the wiggler connection. Do you maybe remember what errors? Here is what I get when I try to get it going: OpenOCD 0.1.0. C:\Program Files\OpenOCD\0.1.0\bin>openocd -f parport_lpt1.cfg -f STM32F10x.cfg Open On-Chip Debugger 0.1.0 (2009-01-21-21:15) Release BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS $URL: https://kc8apf@svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.1.0/src/openocd.c $ jtag_speed: 0 Error: missing privileges for direct i/o Runtime error, file "command.c", line 456: Open OCD 0.2.0. C:\Program Files\OpenOCD\0.2.0\bin>openocd -f parport_lpt1.cfg -f STM32F10x.cfg Open On-Chip Debugger 0.2.0 (2009-07-18-09:50) Release $URL: http://svn.berlios.de/svnroot/repos/openocd/tags/openocd-0.2.0/src/openocd.c $ For bug reports, read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS parport port = 888 jtag_speed: 0 jtag_nsrst_delay: 500 jtag_ntrst_delay: 500 Error: Translation from khz to jtag_speed not implemented Error: missing privileges for direct i/o Runtime error, file "command.c", line 469: As you can see there are two repetative errors Error: missing privileges for direct i/o Runtime error, file "command.c" What are the odds that this is windows 7 related?

Hi, I have a DIY wiggler made from schematics nILS posted, and a 0.4.0. version of OpenOCD. I'm stuck and need help. When I run OpenOCD i get this: C:\Program Files\OpenOCD\0.4.0\bin>openocd -f %MIOS32_PATH%\etc\openocd\interface\parport_lpt1.cfg -f %MIOS32_PATH%\etc\openocd\target\STM32F10x.cfg Open On-Chip Debugger 0.4.0 (2010-02-22-19:05) Licensed under GNU GPL v2 For bug reports, read http://openocd.berlios.de/doc/doxygen/bugs.html parport port = 0x378 Runtime error, file "C:\Users\Joc\Desktop\MIDIBox\trunk\etc\openocd\interface\parport_lpt1.cfg", line 11: invalid command name "jtag_speed" I also tried wit 0.2.0. version of OpenOCD but with no luck. I have a feeling it's a minor obstacle but I'm a total noob. Does anybody know where can I find an OpenOCD 0.1.0 installer (for Windows)? Also, does the Core have to be connected to the wiggler at all time? BTW, is it normal for a LED to lighten up when the wiggler is connected to the parallel port? By the schematics I thought that the wiggler needed a power supply from the STM32 core :unsure:

Hi, I'm also planing to work on a new project and I did some research (btw very very nice work with the tutorials :frantics:) but I didn't know that you can assign free I/O pins to i.e. AINs. Does this mean that the number of pots, buttons, LEDs or even MIDI IN/OUT ports is limited by the number of free I/O pins (and my programing skills)? If so than this Core32 is more powerful than I thought :drool: One more question just to make sure, I presume that there is no need to ground the unused pins on the STM32 like the analog input pins on the PIC core, right? Best regards

Hi, I was also planning to make a new project including a CODEC from TI for line outputs on my MIDIbox. So far I'm going for the PCM1792A (a x2 output, 132dB SNR, 24-bit, 192 kHz Stereo DAC), but I'll have to see how to implement it in the MIDIbox (using STM32 core). Keep us posted!!! :rolleyes:

How is it going with the buttons?

Yeah I found that out recently but tnx anyhow. Maybe I'll post a video if I get the time and the camera ;) Bye

Tnx very much for that...sincerely I didn't think that could be done that way

Yeah but on which channel and note??? :P I didn't develop my own firmware and I don't know the DOUT channel of other accessible firmware...

Why? Btw I'm in the programming phase for my controller so as soon as I figure out the Traktor LED control I'll let you know.

Tnx for the info about the vmidibox, I didn't know for that. Although I can't "assign" LEDs to pots (or can I ???) only buttons, and therefore I'll need customized firmware for my controller... I'm currently using MTE's Traktorizer firmware...you can see from the picture it's not suited for my needs. Anubis.JPG Anubis.JPG

Yes I did and now I'm trying to make the app which is not going as I planned. I didn't manage the "Setup and install" for the app development. Also I didn't quite figure out the app development (read program logic). To be honest I really have little time for app development research (because of the other things on my mind) so if you have some directions I'll be glad if you share it with me. I was searching the forum for that matter but it takes a lot of time to get some useful info. I was also wondering how to setup Microsoft Visual Studio C++ for the app development? ???

Fond the problem. The power supply, the power connector on the case to be more accurate. It was making a short circuit which apparently effected the PIC long enough to make him go bad. Anyway tnx to everybody who helped!!! Regards