-
Posts
15,199 -
Joined
Content Type
Profiles
Forums
Blogs
Gallery
Everything posted by TK.
-
Linux - Mios8 - Toochain - make - problems
TK. replied to Phatline's topic in MIDIbox Tools & MIOS Studio
What is the output of: which sdcc ? Best Regards, Thorsten. -
So wie beim MBHP_DIO Board. Ich weiss nicht, warum "SRIO num_sr=2" nicht funktioniert, doch wenn es mit num_sr=4 klappt, ist das in Ordnung. "num_sr=2" macht von der Laufzeit her keinen grossen Unterschied. Gruss, Thorsten.
-
Linux - Mios8 - Toochain - make - problems
TK. replied to Phatline's topic in MIDIbox Tools & MIOS Studio
Seems that this wiki page is outdated. It has been written 2009, at this point of time SDCC 2.8.0 was the "latest and greatest" version. Meanwhile a newer SDCC version is provided by default, but it isn't compatible with MIOS8 anymore. Hopefully a Linux user who was able to install the tools successfully will update this page, otherwise many people will come across this inconsistent information in future and they will be stucked (like you). However, I'm unsure how I can help you. For me it looks like you did some changes in the original files which come with the MIOS8 repository. Unfortunately my crystal ball shows only white smoke there ;-) If you enter: cat $MIOS_BIN_PATH/mios-sdcc what do you see at the last line? It should be: sdcc --asm="${MIOS_SHELL} ${MIOS_BIN_PATH}/mios-gpasm -fixasm" $@ If you see something else (e.g. a direct path reference to sdcc), then we found out that you've modified this file... ;) Best Regards, Thorsten. -
Linux - Mios8 - Toochain - make - problems
TK. replied to Phatline's topic in MIDIbox Tools & MIOS Studio
As mentioned above: you've to use SDCC 2.8.0, no other version will work properly. This message: make: /bin/share/sdcc: Kommando nicht gefunden tells you, that the sdcc command hasn't been found under /bin/share/sdcc This isn't a problem with 2.8.0, but with your unix shell setup. The big question is: why is it searched under /bin/share, and not under /usr/local/bin or wherever you installed sdcc What surprises me: you are able to retrieve the version - how exactly did you do that? Best Regards, Thorsten. -
Hier findest Du ein LED_MATRIX_PATTERN Konfigurationsbeispiel fuer 11 LEDS: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Fdefault%2Fdefault.ngc # LED_MATRIX_PATTERNs LED_MATRIX_PATTERN n=1 pos= 0 pattern=1000000000000000 LED_MATRIX_PATTERN n=1 pos= 1 pattern=1100000000000000 LED_MATRIX_PATTERN n=1 pos= 2 pattern=1100000000000000 LED_MATRIX_PATTERN n=1 pos= 3 pattern=1110000000000000 LED_MATRIX_PATTERN n=1 pos= 4 pattern=1110000000000000 LED_MATRIX_PATTERN n=1 pos= 5 pattern=1111000000000000 LED_MATRIX_PATTERN n=1 pos= 6 pattern=1111000000000000 LED_MATRIX_PATTERN n=1 pos= 7 pattern=1111100000000000 LED_MATRIX_PATTERN n=1 pos= M pattern=1111110000010000 LED_MATRIX_PATTERN n=1 pos= 8 pattern=1111111000000000 LED_MATRIX_PATTERN n=1 pos= 9 pattern=1111111100000000 LED_MATRIX_PATTERN n=1 pos=10 pattern=1111111100000000 LED_MATRIX_PATTERN n=1 pos=11 pattern=1111111110000000 LED_MATRIX_PATTERN n=1 pos=12 pattern=1111111110000000 LED_MATRIX_PATTERN n=1 pos=13 pattern=1111111111000000 LED_MATRIX_PATTERN n=1 pos=14 pattern=1111111111000000 LED_MATRIX_PATTERN n=1 pos=15 pattern=1111111111100000 LED_MATRIX_PATTERN n=2 pos= 0 pattern=1111110000000000 LED_MATRIX_PATTERN n=2 pos= 1 pattern=0111110000000000 LED_MATRIX_PATTERN n=2 pos= 2 pattern=0111110000000000 LED_MATRIX_PATTERN n=2 pos= 3 pattern=0011110000000000 LED_MATRIX_PATTERN n=2 pos= 4 pattern=0001110000000000 LED_MATRIX_PATTERN n=2 pos= 5 pattern=0001110000000000 LED_MATRIX_PATTERN n=2 pos= 6 pattern=0000110000000000 LED_MATRIX_PATTERN n=2 pos= 7 pattern=0000010000000000 LED_MATRIX_PATTERN n=2 pos= M pattern=0000111000010000 LED_MATRIX_PATTERN n=2 pos= 8 pattern=0000010000000000 LED_MATRIX_PATTERN n=2 pos= 9 pattern=0000011000000000 LED_MATRIX_PATTERN n=2 pos=10 pattern=0000011000000000 LED_MATRIX_PATTERN n=2 pos=11 pattern=0000011100000000 LED_MATRIX_PATTERN n=2 pos=12 pattern=0000011110000000 LED_MATRIX_PATTERN n=2 pos=13 pattern=0000011110000000 LED_MATRIX_PATTERN n=2 pos=14 pattern=0000011111000000 LED_MATRIX_PATTERN n=2 pos=15 pattern=0000011111100000 LED_MATRIX_PATTERN n=3 pos= 0 pattern=1000000000000000 LED_MATRIX_PATTERN n=3 pos= 1 pattern=0100000000000000 LED_MATRIX_PATTERN n=3 pos= 2 pattern=0100000000000000 LED_MATRIX_PATTERN n=3 pos= 3 pattern=0010000000000000 LED_MATRIX_PATTERN n=3 pos= 4 pattern=0010000000000000 LED_MATRIX_PATTERN n=3 pos= 5 pattern=0001000000000000 LED_MATRIX_PATTERN n=3 pos= 6 pattern=0000100000000000 LED_MATRIX_PATTERN n=3 pos= 7 pattern=0000010000000000 LED_MATRIX_PATTERN n=3 pos= M pattern=0000111000010000 LED_MATRIX_PATTERN n=3 pos= 8 pattern=0000010000000000 LED_MATRIX_PATTERN n=3 pos= 9 pattern=0000001000000000 LED_MATRIX_PATTERN n=3 pos=10 pattern=0000000100000000 LED_MATRIX_PATTERN n=3 pos=11 pattern=0000000100000000 LED_MATRIX_PATTERN n=3 pos=12 pattern=0000000010000000 LED_MATRIX_PATTERN n=3 pos=13 pattern=0000000001000000 LED_MATRIX_PATTERN n=3 pos=14 pattern=0000000001000000 LED_MATRIX_PATTERN n=3 pos=15 pattern=0000000000100000 LED_MATRIX_PATTERN n=4 pos= 0 pattern=0000010000000000 LED_MATRIX_PATTERN n=4 pos= 1 pattern=0000010000000000 LED_MATRIX_PATTERN n=4 pos= 2 pattern=0000111000000000 LED_MATRIX_PATTERN n=4 pos= 3 pattern=0000111000000000 LED_MATRIX_PATTERN n=4 pos= 4 pattern=0000111000000000 LED_MATRIX_PATTERN n=4 pos= 5 pattern=0001111100000000 LED_MATRIX_PATTERN n=4 pos= 6 pattern=0001111100000000 LED_MATRIX_PATTERN n=4 pos= 7 pattern=0001111100000000 LED_MATRIX_PATTERN n=4 pos= M pattern=0011111110010000 LED_MATRIX_PATTERN n=4 pos= 8 pattern=0011111110000000 LED_MATRIX_PATTERN n=4 pos= 9 pattern=0011111110000000 LED_MATRIX_PATTERN n=4 pos=10 pattern=0011111110000000 LED_MATRIX_PATTERN n=4 pos=11 pattern=0111111111000000 LED_MATRIX_PATTERN n=4 pos=12 pattern=0111111111000000 LED_MATRIX_PATTERN n=4 pos=13 pattern=0111111111000000 LED_MATRIX_PATTERN n=4 pos=14 pattern=1111111111100000 LED_MATRIX_PATTERN n=4 pos=15 pattern=1111111111100000 Gruss, Thorsten.
-
It's a simple DOUT based DAC, the ASCII based schematic can be found in the setup_* files (e.g. http://svnmios.midibox.org/filedetails.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fsequencers%2Fmidibox_808%2Fsetup_seq_dr_default.asm ) ;; CV values can also be output via DOUT shift registers ;; This option is sufficient to control the "velocity" of drum instruments, and it's cheap as well! ;; We expect following connections: ;; ;; DOUT 160k ;; D7 ---o---/\/\/\---* ;; 80.6k | ;; D6 ---o---/\/\/\---* ;; 40.2k | ;; D5 ---o---/\/\/\---* ;; 20.0k | ;; D4 ---o---/\/\/\---* ;; 10.0k | ;; D3 ---o---/\/\/\---* ;; 5.1k | ;; D2 ---o---/\/\/\---*----o CV Out ;; 220 Ohm ;; D1 ---o---/\/\/\--------o free assignable trigger ;; 220 Ohm ;; D0 ---o---/\/\/\--------o another free assignable trigger ;; ;; The DOUTx channels are matching with the AOUT channels as specified in the DEFAULT_TRKINFO table above. ;; Allowed values: 1-16 (selects DOUT shift register) or 0 to disable ;; Ensure that DEFAULT_NUMBER_SR is high enough so that all DOUTs are updated. #define DEFAULT_CV_DOUT_SR1 4 #define DEFAULT_CV_DOUT_SR2 5 #define DEFAULT_CV_DOUT_SR3 6 #define DEFAULT_CV_DOUT_SR4 7 #define DEFAULT_CV_DOUT_SR5 8 #define DEFAULT_CV_DOUT_SR6 9 #define DEFAULT_CV_DOUT_SR7 10 #define DEFAULT_CV_DOUT_SR8 11 #define DEFAULT_CV_DOUT_SR9 12 #define DEFAULT_CV_DOUT_SR10 13 #define DEFAULT_CV_DOUT_SR11 14 #define DEFAULT_CV_DOUT_SR12 15 #define DEFAULT_CV_DOUT_SR13 16 #define DEFAULT_CV_DOUT_SR14 0 #define DEFAULT_CV_DOUT_SR15 0 #define DEFAULT_CV_DOUT_SR16 0 Best Regards, Thorsten.
-
When you search for SPEAKJET_PORT in the source files, you will find the places which need to be adapted. Direct port access is a very dirty method (actually it was a bad idea to release the app this way...) Currently I'm not able to test this by myself, but it could make sense to access the module via J5 IOs instead. A tutorial can be found under: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F008_j5_outputs%2F Best Regards, Thorsten.
-
It seems that you are using LED digits with common anode (my examples are pre-configured for common cathode devices). So, instead of: # HW definitions for "Common Cathode" Digits # see also http://www.ucapps.de/midibox_ng/mbng_led_digits_mtc.pdf DOUT_MATRIX n=1 rows=8 sr_dout_r1=1 inverted_row=0 mirrored_row=0 sr_dout_sel1=2 inverted_sel=0 DOUT_MATRIX n=2 rows=8 sr_dout_r1=3 inverted_row=0 mirrored_row=0 sr_dout_sel1=4 inverted_sel=0 just write: # HW definitions for "Common Anode" Digits DOUT_MATRIX n=1 rows=8 sr_dout_r1=1 inverted_row=1 mirrored_row=0 sr_dout_sel1=2 inverted_sel=1 DOUT_MATRIX n=2 rows=8 sr_dout_r1=3 inverted_row=1 mirrored_row=0 sr_dout_sel1=4 inverted_sel=1 Best Regards, Thorsten.
-
Concerning Program Change: there is a newer (unreleased) MBSEQ V4 version which provides a track based program change selection. Maybe you find it useful? -> see Best Regards, Thorsten.
-
Hi, are you using 10k or 1k pots? In any case, it could work better if you connect the Ground/5V lines of the pots to J2 of the core module. Best Regards, Thorsten.
-
@Pete: thank you very much for pointing this out! Indeed, I forgot to forward MIDI event generated by the matrix to the MIDI file recorder. @Johnc: please try this version: http://www.ucapps.de/mios32/midio128_v3_020_pre1.zip Best Regards, Thorsten.
-
Ok, dann hast Du mehr als 2 DOUT Shift Register oder 2 DIN Shift Register hintereinandergehaengt? Gruss, Thorsten.
-
Da Deine MIDIbox auf einem MBHP_CORE_STM32F4 basiert, kannst Du zwei MBHP_MIDI_IO Module hintereinanderhaengen: http://www.ucapps.de/mbhp_midi_io.html Damit ergeben sich schonmal 4 MIDI IN und 4 MIDI OUT. Zusaetzlich noch ein Quad-IIC Board, und Du hast insgesamt 8 MIDI OUTs 16 Gate Outs: wie bereits von Ungleichklang erwaehnt, tut sich da gerade etwas, deshalb bitte auf die aktualisierte Dokumentation warten. Es gibt 8 Gates, die mit den analogen CV Ausgaengen zusammenhaengen, und 64 zusaetzliche Gates (die man auch optional als Drum-Trigger verwenden kann). Diese legt man auf DOUT Shift Register. Jedes Shift Register bietet 8 Ausgaenge. Ein MBHP_DOUTX4 Modul hat 4 Shift Register, somit 32 Ausgaenge. Gruss, Thorsten.
- 85 replies
-
Here are some tutorials: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Ftutorials%2F And here is a minimal application which shows how to force MIDI notes to a scale: http://svnmios.midibox.org/listing.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fprocessing%2Fmidi_force_to_scale%2F It requires some self-education to put these pieces together, there is especially no additional literature about the MIDIbox platform aside from the information on ucapps.de, wiki.midibox.org and the SVN repositories. Best Regards, Thorsten.
-
Perfekter Umbau! :-) MIDI3: siehe diesen Schaltplan: http://www.ucapps.de/mbhp/mbhp_core_lpc17_midi3_midi4_extension.pdf Zur MBNG Latenz: die laesst sich seit V1.032 mit dem "SRIO num_sr=<anzahl-der-shift-register>" erheblich verringern. In Deinem Fall (zwei DIN, zwei DOUT) genuegt "SRIO num_sr=2" Gruss, Thorsten.
-
Linux - Mios8 - Toochain - make - problems
TK. replied to Phatline's topic in MIDIbox Tools & MIOS Studio
You've to use sdcc 2.8.0, please don't try any other version because only this release has been qualified. A linux version can be downloaded from: http://sourceforge.net/projects/sdcc/files/sdcc-linux-x86/2.8.0/ The package contains a INSTALL.txt file, just follow the instructions. Once SDCC has been installed (e.g. under /usr/local/bin), the "sdcc --version" command should return SDCC : mcs51/gbz80/z80/avr/ds390/pic16/pic14/TININative/xa51/ds400/hc08 2.8.0 #5117 (Mar 23 2008) (Mac OS X i386) If it returns another string, your PATH variable doesn't reference the correct binary, in this case try to uninstall the other versions that you've installed so far. Once this has been done, the original mios8 makefiles will work without modifications (no need to set special flags etc.) Best Regards, Thorsten. -
BLM16X4.ngc - Invalid flag in EVENT_LED_MATRIX
TK. replied to jab's topic in Testing/Troubleshooting
Hi, you are right, this is a bug in the parser. Here a link to the updated firmware: http://www.ucapps.de/mios32/midibox_ng_v1_032_post1.zip Best Regards, Thorsten. -
You've to specify the first ID to which the LEDs should be assigned with "led_emu_id_offset=<id>" in the DOUT_MATRIX configuration. See also http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fapps%2Fcontrollers%2Fmidibox_ng_v1%2Fcfg%2Ftests%2Frgb_1.ngc Best Regards, Thorsten.
-
Ok, I can add these special LED functions without much effort. This is already possible in conjunction with the modulation matrix! :) Several operators are available, such as >=, <= but also S&H (Sample & Hold) The operations can be applied on two analog inputs, but also between an analog input and an internal modulation source (such as a LFO or ENV) Best Regards, Thorsten.
-
Yes, V1.017 is the latest one. Could you please try the following: press & hold the blue button on the STM32F4DISCOVERY board, and then shortly trigger the black button (to reset the device) Keep the blue button pressed! This enforces bootloader mode. Now re-open MIOS Studio. Maybe you've to select a new MIDI IN/OUT device (but mostly the previous setting will work as well). Check query (blue button still pressed) - does this work? Upload a firmware (blue button still pressed) - does this work? Release the blue button after firmware upload so that the application will be started. Best Regards, Thorsten.
- 20 replies
-
I take this problem report serious once somebody notices a similar problem under Windows or MacOS Best Regards, Thorsten.
-
Are you using the latest MIOS Studio release 2.4.6? With this version the message should only appear if after the invocation of MIOS Studio the communication to a LPC17 core was successfully working, and thereafter you tried to connect to a STM32 core and the communication was failing. Best Regards, Thorsten.
- 20 replies
-
I agree, not enough input to help you. Best Regards, Thorsten.
-
:hyper:
-
I spent some time to make this happen: MBSEQ finally provides a "Track Instrument" configuration page: o new page: "Track Instrument" Can be selected with MENU->EVNT->Trk Inst (GP #8) or from the main page (after Track Event item) Allows to configure the MIDI port, channel and instrument name. o the new Track Instrument page also allows to select Program Change and Bank (Low/High byte) If activated, these parameters will be sent when the sequencer is started and on pattern changes. Please note: a program and bank change can stall your synth so that the first note could be delayed! Use this function only when the device can handle patch changes quickly! could you please help me to check if it works as expected? Prebuilt firmware: http://www.ucapps.de/mios32/midibox_seq_v4_087_pre5.zip Best Regards, Thorsten.