TK.

yes yes - have a look into the project_build/project.sym file, it lists the addresses of all symbols The RAM section starts at 0x20000000, it's at the bottom of the file This file is also useful to find out, how much memory is allocated by the variables for the case that you touch the limits again and have to start with optimization measures. Best Regards, Thorsten.

Could this be a problem with your audio jacks, e.g. left and right channel soldered to the wrong pins? Best Regards, Thorsten.

Actually it means, that large RAM arrays have to be assigned to the AHB RAM (second half of the 64k RAM) in C code. This can be done with (example for an u8 array): u8 __attribute__ ((section (".bss_ahb"))) my_large_array[VERY_HIGH_NUMBER]; the "extern" statement is required when you want to import the symbol into another .c file (therefore you will mostly find "extern" in header files) Actually all variables are "extern" (=global) if you don't explicitely make them local with the "static" attribute. yes, "static" makes the variable local, and "const" ensures that it will be located into flash memory. Best Regards, Thorsten.

yes, it uses buflcd as well (meanwhile) :) Best Regards, Thorsten.

Thanks for reporting - the labels are not copied yet, this will work with the next release. Best Regards, Thorsten.

Hallo, hier die Default-Zeile aus dem Konfigurationsfile: #MATRIX;Number;USB1;USB2;USB3;USB4;IN1;IN2;IN3;IN4;RES1;RES2;RES3;RES4;OSC1;OSC2;OSC3;OSC4;Mode;Chn;Arg;DIN_SR;DOUT_SR MATRIX;1;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;0;0 [/code] Sie existiert insg. 16 Mal, die Matrix-Nummer steht in der zweiten Spalte. In den letzten beiden Spalten werden die DIN/DOUT shift register zugewiesen. Hier ein Beispiel, bei dem 16 Matrizen fuer dedizierte DIN Register, und einem DOUT Register konfiguriert werden: [code] #MATRIX;Number;USB1;USB2;USB3;USB4;IN1;IN2;IN3;IN4;RES1;RES2;RES3;RES4;OSC1;OSC2;OSC3;OSC4;Mode;Chn;Arg;DIN_SR;DOUT_SR MATRIX;1;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;1;1 MATRIX;2;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;2;1 MATRIX;3;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;3;1 MATRIX;4;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;4;1 MATRIX;5;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;5;1 MATRIX;6;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;6;1 MATRIX;7;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;7;1 MATRIX;8;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;8;1 MATRIX;9;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;9;1 MATRIX;10;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;10;1 MATRIX;11;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;11;1 MATRIX;12;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;12;1 MATRIX;13;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;13;1 MATRIX;14;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;14;1 MATRIX;15;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;15;1 MATRIX;16;1;0;0;0;1;0;0;0;0;0;0;0;1;0;0;0;1;1;0x30;16;1 Achtung: wenn Du das DEFAULT.MIO File direkt editierst, solltest Du die bisherigen MATRIX Zeilen entweder durch die neuen ersetzen, oder die neuen Zeilen am Ende des Files einfuegen (so dass die Definitionen aus den vorigen Zeilen ueberschrieben werden) Gruss, Thorsten.

This is the NRPN chart, the CC chart is here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsynthesizers%2Fmidibox_sid_v2%2Fdoc%2Fmbsidv2_cc_chart.txt&peg=881 It's strange that your MB6582 is freezing when CCs 0..19 are received - does anybody else ever noticed the same issue? Best Regards, Thorsten.

For the records: http://www.ucapps.de/mbhp/auaimbctg.pdf Best Regards, Thorsten.

Hallo Gerd, dass sich das so pragmatisch loesen laesst, haette ich nun nicht gedacht... ;-) Die Multiplexer-Option laesst sich im setup_midibox64.asm File deaktivieren: ; Number of connected pots ; Allowed values: 1-64 #define DEFAULT_NUMBER_POTS 8 ; number of connected pots ; ; Multiplexers (AINX4 modules) connected? -> set this value to 1 ; No multiplexer connected= -> set this value to 0, allowed number of pots in this case: 1-8 #define DEFAULT_MUX_ENABLED 0 ; enable multiplexers [/code] allerdings muesstest Du nach der Aenderung ein neues .hex File generieren, das geht mit der MIOS8 Toolchain (hauptsaechlich: gputils und mingw) Gruss, Thorsten.

Very cool! :) Best Regards, Thorsten.

Den Papierkatalog erhielt ich mir der letzten Bestellung, er ist sogar auf Deutsch verfasst und bietet eine recht gute Uebersicht ueber das Sortiment. Gruss, Thorsten.

It should work with following configuration in mios32_config.h: #define BUFLCD_NUM_DEVICES 8 #define BUFLCD_COLUMNS_PER_DEVICE 20 #define BUFLCD_MAX_LINES 4 [/code] The text output has to be adapted in mm_lcd.c Best Regards, Thorsten.

Last update: a 10 uF cap should be added between the reset pins and ground to stretch the reset after power-on. -> http://www.ucapps.de/mbhp/mbhp_lcd_ssd1306_single_mios32.pdf The LCD driver now waits for 500 mS before the OLEDs are initialized. This delay is especially required if the "fast_boot" option has been enabled in the bootloader. Best Regards, Thorsten.

I fixed this in http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2FLPC17xx%2Fmios32_board.c The issue wasn't related to the USB PPWR option, but to the activated pull-up device, which conflicted with the D7 driver. As a result the voltage level at this pin was a bit lower than for the other ones, and the SSD1306 OLED doesn't "like this". Could you please check if this solution also works at your side? Next step is to improve the reset circuit for the SSD1306 OLEDs, because it seems that they are sporadically not properly initialized after power-on. A cap which stretches the reset pulse should help. Best Regards, Thorsten.

Wow, this is an interesting input! I haven't noticed this problem with my own SSD1306 displays yet, since they are connected to a minimalistic breadboard based CORE_LPC17 module (-> http://www.ucapps.de/mbhp/mbhp_core_lpc17_miniproto1.jpg) The connection between J15:D7 and P1.19 is intended, the CLCD driver uses it to poll the busy bit. I thought that I disabled the USB PPWR option, but it seems that this isn't the case. While checking the schematic, I also noticed that there might be a problem with the BSL_HOLD function which is connected to J15:RW (more about this topic if it turns out that my assumptions are true). I will check this today and evtl. release a new universal LCD driver. Best Regards, Thorsten.

How does it sound when two musicians are shaking hands? :) Great work! Best Regards, Thorsten.

Thanks for the important detail! I don't use the RATOPC function by myself, and therefore assumed that the glitch was introduced with the latest enhancements for the guide track... The behaviour of RATOPC sounds faulty, I will check this as well. Best Regards, Thorsten.

No, "cleaning error" is new to me. Are you trying this from codeblocks? I've no experiences with this IDE. My proposal was to enter "make clean" in the command shell (of your operating system) Alternatively just remove the "project_build" directory, this is what "make clean" actually is doing. Best Regards, Thorsten.

Your alternative resistor network should work (and doesn't influence the upload). The failing upload is strange. It works at my side under Windows (without special driver) and MacOS. Not tested under Linux, but I guess that you don't use Linux anyhow... You are using USB, right? Could you try it with the Korg USB Driver? See Best Regards, Thorsten.

Hi, this isn't supported by the firmware, some changes are required. Yes, a 8x8 matrix which consist of two DOUT SRs + sink driver transistors directly connected to the end of the frontpanel PCB would be sufficient Best Regards, Thorsten.

I used it intensively between 2002..2006, thereafter I used intensively the MIDI router project till 2008, thereafter I used intensively the GM5 based MIDI interface, currently I use intensively MBHP_CORE_LPC17 based solutions. I don't know if Mike can sell you a preburned PIC. Best Regards, Thorsten.

So, your PIC is already running with bootloader v1.2? Best Regards, Thorsten.

Hi, we've another thread (-> ) where ForestCat reports problems with the PIC16F88 based firmware (we're also in contact via email to solve this) Therefore: currently I can only recommend the PIC18F452 based variant, since this is the only one which has been used by myself in the past. Best Regards, Thorsten.

Nice work! :) I think that the a "deadband" algorithm would be sufficient, it's already integrated into MIOS -> MIOS_AIN_DeadbandSet You could also dynamically decrease the deadband if your application notices a fast movement, and set it to a higher value again if it stops. The C implementation of the deadband can be found in the MIOS32 variant under: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmios32%2FLPC17xx%2Fmios32_ain.c This one even supports a "spike filter", which could be helpful for your application as well! :) Best Regards, Thorsten.

Hallo Marxon, wenn ich Dich jetzt nicht falsch verstanden habe, gibt es diese Funktion bereits: es ist der Assign Layer in der ENV Sektion. In diesem Layer kann man mit den 5 ENV Encodern die gerade angezeigten Parameter direkt modifizieren. Gruss, Thorsten.