TK.

Hi, the STM32F103RB is a very limited processor, it has only 128k flash and especially only 20kb RAM (instead of 64kb of the RE). Therefore it normally doesn't make much sense to save 1..2$ -> just use the RE and you are fully binary compatible. I fear that most "real" applications won't run on the RB, and as you already noticed, you will also find incompatibility issues and "random effects" I guess that they are mostly related to RAM overruns if you are trying to run an application compiled for RE on a RB. Due to historical reasons I've a special linker file under etc/ld/STM32F10x/STM32F103RB.ld which is suitable for the limited memory specs. It will be automatically selected if MIOS32_PROCESSOR is set to STM32F103RB instead of STM32F103RE After this change, type "make clean", and thereafter "make" to recompile the complete application. I don't know if this change is sufficient, since I haven't tried this since more than 2 years... If the application is too big, the linker will fail. Best Regards, Thorsten.

Hallo, das "arm-none-eabi-gcc" Kommando wird nicht gefunden - Du musst noch die MIOS32 Toolchain fuer WIndows installieren. Die gibt es unter ftp://ftp.lansystems.co.uk/pub/midibox Filename: mios32_toolchain_windows_20101024.zip Ich werde jetzt nochmal eine Checkliste schreiben, zugegebenermassen sind die Informationen unter http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core etwas verwirrend, da hier die Installation fuer "normale Anwender" nicht exakt beschrieben ist. Gruss, Thorsten.

Yes: - open MIOS Terminal - mount the SD Card with the "msd on" command - open the file "MBSEQ_GC.V4" with a text editor - search for "CV_AOUT_Type", set the value to 3 for the AOUT_NG module - save the file - open the file "SESSIONS/DEF_V4L/MBSEQ_C.V4" - search for "MIDI_DefaultPort", set the value to 128 for the AOUT port - save the file - unmount the SD Card - reboot your MBSEQ V4L -> done :) Unfortunately you haven't mentioned where you are living, therefore I fear that I can't give you an individual hint where to buy a single chip. Note that I'm planning to create a new "low cost" interface which will be based on an inexpensive but sufficient DAC from Microchip, which can be purchased at Reichelt. It will only support two channel, but thats sufficient for most purposes. According to the schematic: http://www.ucapps.de/midibox_seq/mbseq_lite_blm.pdf "LED cathodes (short leg) at right side!" This means in other words: LED anodes (long leg) at left side! Best Regards, Thorsten.

The LPCXPRESSO features a 8k EEPROM. It can be accessed through the $MIOS32_PATH/modules/eeprom routines. Programming example: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2F&# see especially: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2FMakefile (search for EEPROM) http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2Fsrc%2Fmios32_config.h (search for EEPROM http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_kb_v1%2Fsrc%2Fpresets.c Note that this is work in progress, future versions will store much more informations in EEPROM, but will also get more complex (therefore harder to understand). The EEPROM isn't used by the MIOS128 application if this was your question. If you use a different magic number (EEPROM_MAGIC_NUMBER, defined in mios32_config.h), the EEPROM content will be initialized by preset.c to ensure data consistence. Best Regards, Thorsten.

I only had a quick look... this project isn't really for interest. It doesn't support STM32, but PIC32 And it seems that some code has been copied from the internet without referring to the original authors as required by the GPL. E.g. the original author of p32/include/pinguino/core/printf.c is Georges Menie (http://www.menie.org), the stdarg version was contributed by Christian Ettinger But in the Pinguino source Regis Blanchot states that he is the author. Best Regards, Thorsten.

Ist wohl ein Bug in der aktuellen IDE Version - ich hoffe, dass sehr bald eine neue rauskommt. /Update: Ich habe heute die aktuelle IDE Version bei mir installiert - sie funktioniert, nur muss man vor dem Flashen noch ein passendes Projekt erstellen. Dies habe ich nun auf der http://www.ucapps.de/mbhp_core_lpc17.html Seite mit neuen Snapshots dokumentiert. Gruss, Thorsten.

Ist wohl ein Bug in der aktuellen IDE Version - ich hoffe, dass sehr bald eine neue rauskommt. Gruss, Thorsten.

It means that analog inputs will be available at pin number #56..63 - thats ok But please note: you don't need a 4051 multiplexer if only 8 channels are required. You even don't need a 74HC595 for this minimal solution. Instead you would only need the MCP3208, pots can be directly connected to the 8 ADC inputs! + J2, R1, C4, C5, C6 - done! Normally it's faster to build such a circuit on verboard instead of doing the timeconsuming layout + etching. Best Regards, Thorsten.

Interesting! Was the other 595 a 74HCT595 or a 74HC595 ... or just a re-used part with "unknown state"? Best Regards, Thorsten. Btw.: now where more and more people are using the MBHP_CORE_LPC17 module, a port of the LCD interconnection test is on my Agenda... :)

Thanks again - the third error: wrong link, wrong enumeration, wrong supply voltage - ok, I created the schematic at new year's eve and was in hurry... ;-) The supply voltage is 3.3V since the output pins of the LPC17 UARTs don't support open drain mode which would allow to pull the voltage to 5V. Note: using 3.3V for the 1k pull-up at the output of the optocoupler shouldn't cause an issue. I changed it this way to avoid one additional cable to a +5V pin. Best Regards, Thorsten.

Thank you! Fixed Best Regards, Thorsten.

This is the wrong schematic, it fixes a problem with a problematic MIDI device, but it isn't standard! Here the correct link: http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf (I fixed the webpage and added the same link to the MBHP_CORE_LPC17 page now) Best Regards, Thorsten.

MIDIO128 V3.006 is available now Finally the "128" also stands for 128 analog inputs! :) MIDIO128 V3.006 ~~~~~~~~~~~~~~~ o support for two MBHP_AINSER64 modules: up to 128 analog pins can be scanned! o improved MIDI OUT throughput [/code] Best Regards, Thorsten.

The firmware is located under: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmbhp_mf_v3%2F Best Regards, Thorsten.

I got the prototype PCBs and successfully tested the module today! It's officially released now: http://www.ucapps.de/mbhp_ainser64.html Next step is to ask SmashTV for providing the new module in his MIDIbox shop. :) Best Regards, Thorsten.

V4L.057 is available now: MIDIboxSEQ V4L.057 ~~~~~~~~~~~~~~~~~~ o improved MIDI OUT throughput [/code] Christian: could you please check if this relaxes the "bottleneck issue" with your setup? Best Regards, Thorsten.

Me too - this was the original intention of this page. On the other hand I agree with StuartM that the handling is unusual. An option for the behaviour: only if much more than one user requests this! :) Best Regards, Thorsten. V4.057 is available now - it's only interesting for LPC17 users: MIDIboxSEQ V4.057 ~~~~~~~~~~~~~~~~~ o improved MIDI OUT throughput for LPC17 [/code] Best Regards, Thorsten.

Vorsicht! Gleich-riecht-er! ;-) Gruss, Thorsten.

Hallo Bernhard, haeng' das .asm File doch bitte mal an diesen Thread an (-> "Use Full Editor", "-> "Attach Files") so koennte ich es editieren, kompilieren, und Dir das .hex File zukommen lassen. Gruss, Thorsten.

Hi Stefan, the most detailed description can be found in the source code... ;-) Best Regards, Thorsten.

Open and Closed HH can't be played at the same time, because they share the same voice. Btw.: similar to a TR808, "good" sample based drum samplers which allow to group samples, and a real HiHat! ;-) Best Regards, Thorsten.

Should work with the appr. code! :) Best Regards, Thorsten.

J10 pins are configured as inputs by default. Therefore I'm a bit biased: no, you don't have to initialize the pins (again), on the other hand it's good programming practice to initialize IO pins explicitly for the intended mode. Why do you think that it would be better to skip the initialization? Buttons connected to J10: take tutorial #005 as an example and replace J5 by J10 Btw.: I gave you access to the programmers lounge where you will find more background informations. Best Regards, Thorsten.

Here the thread where the MBFM drum behaviour has been discussed: And here the link to a beta version of the upcoming release: http://www.ucapps.de/mios/midibox_fm_v1_4d.zip Best Regards, Thorsten.

Yes, you can also connect encoders to J10. The MIOS32 documentation is currently generated for STM32 where this port is not available, but if you look into the source code you will find them: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2FLPC17xx%2Fmios32_board.c Encoder related informations are available in Tutorial #015b: http://www.ucapps.de/mios32_c.html Just replace J5 by J10 -> done! :) Best Regards, Thorsten.