jmayes

Great! That was exactly what I needed. Thankx again for a quick answer, Jmayes

Thank you ilmenator, I am looking at that now. Seems some pins have mios32 def's and some don't, I was hoping there was generic C defs could be used to toggle any pin like with the pic. Can someone put some more light on this? Thankx again all, Jmayes

Hi, I am trying to convert my app from mios8 to mios32. In mios8 I used "PORTCbits.RC0 = 1" to turn a pin on, I can't seem to find an equivalent in mios32. I would like to use the J19 pins if possible. Also is there anything I will need to do to turn off any preexisting drivers or to configure the pins? Thankx for any help someone can provide, Jmayes

I got up this morning with a fresh pair of eyes and found that I had not broken out the mios32_toolchain properly from the windows zip file which left mios32_toolchain in a sub dir instead of on the root of C. After I fixed that everything seems to work fine now. Guess it was just too late when I was working on it last night. Thankx again all for the help! Jmayes

I have followed the windows_mios32_toolchain_core page exactly and pm'd Gecko and he did not install anything I have not so that brings me full circle. Can someone put some light on why I am getting the "arm-none-eabi-gcc" not found error below? P:\info\midi\midi-box\SVN_MIOS32\apps\examples\srio>make rm -f project.hex Creating object file for app.c make: arm-none-eabi-gcc: Command not found make: *** [project_build/app.o] Error 127 Thankx agian all, Jmayes

It's in C:\msys\1.0\ Debug gave me 10 minutes of scrolling info ending in basically the same error Creating object file for app.c Reaping winning child 0x0a04bd08 PID 3724 make: arm-none-eabi-gcc: Command not found Live child 0x0a04bd08 (project_build/app.o) PID 2512 Reaping losing child 0x0a04bd08 PID 2512 make: *** [project_build/app.o] Error 127 Removing child 0x0a04bd08 PID 2512 from chain. It's telling me that "arm-none-eabi-gcc" is not found (or installed) I found this in the SVC instructions; Quickstart STM32 Primer under DOS ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ We assume, that the MIOS32 repository has been downloaded to D:\mios32, and that the Ride7 IDE (which comes with STM32 Primer) has been installed. We won't use the IDE, but build & upload the application from the commandline instead. So, all we need from Ride7 IDE is the gcc compiler: C:\Programs\Raisonance\Ride\arm-gcc and the propritary code upload tool "cortex_pgm.exe" under: C:\Programs\Raisonance\Ride\bin So do I need to install this "Ride7"? If so where do I get it? Thankx again, Jmayes

Getting the following error; P:\info\midi\midi-box\SVN_MIOS32\apps\examples\srio>make rm -f project.hex Creating object file for app.c make: arm-none-eabi-gcc: Command not found make: *** [project_build/app.o] Error 127 Using Win7 pro, Here are my path vars; SET PATH= %PATH%;c:\mios32_toolchain\bin;C:\MSYS\1.0\bin set MIOS32_PATH=/P/info/midi/midi-box/SVN_MIOS32 set MIOS32_BIN_PATH=/P/info/midi/midi-box/SVN_MIOS32/bin set MIOS32_GCC_PREFIX=arm-none-eabi set MIOS32_FAMILY=STM32F10x set MIOS32_PROCESSOR=STM32F103RE set MIOS32_BOARD=MBHP_CORE_STM32 set MIOS32_LCD=clcd I know it's finding the SVN, if I change anything there it bombs out with a "File not found error" Also it takes a very long time (3 minutes+) before the error pops up. Any help would be appreciated! Jmayes

Mine is 64x4 with the 4 being the Amux pins on the core so you would have to rewire to make it work. I just found the BLM-Scanner TK did and it does 8x8 x4 (4 separate 8x8 matrix's) which is exactly what you need, it will take some tweaking but looks like it could work for you. http://www.ucapps.de/midibox_seq_manual_blm.html Good luck! Jmayes

"BINGGGG!" Thats the sound of the light bulb going off in my head. Now things make sense! Thankx again! Jmayes

Yes, the version I have now runs on mios8, each keyboard is scanned in 1ms but I need a deadband between scans which is also 1ms (at present). I think it can be rewritten so it would not need that deadband if I quite using the toggle routine but when I figured out it was 100 times slower then what I needed it put the breaks on the rewrite and mios8. You will have to use a 2nd core for the SAM system but there are 8 analogs on both programs for pots. I don't see it doing all 4 manuals in less then 4ms unless TK can show how to speed up the SIO updates, My ASM is limited in that respect. The hookup is to scan the whole keyboard at once with 2 DINx4 boards rigged with pulldown resistors, then the bussbars are driven with a positive pulse. Jmayes

Thank you Phil for the quick answer, I found that page but it left me somewhat fuzzy on the exact setup required. It implies a real-time SVN hookup. Will I have to access the internet every time I compile? I would much prefer to copy to a drive so I can keep a static complier locked away if I ever have to work on this years down the road. Perhaps I just don't understand clearly yet how the process will work? Thankx again, Jmayes

No, Sorry it's on the example application in C so no ini file, just straight mapping key1=0, key2=1, etc. An offset would be easy to add though. Each keyboard outputs on a different midi channel. At this point it can scan 4 keyboards (3 keyboards + Pedals) in 8ms which might leave for to much latency for some but I could let you try it if you like. Going to port it to the mios32 platform from here, I have to get it up to 10us per keyboard in order to match the scanning of my organ and make it work in tandem. Did you see my SAMS project in the other thread? I am wiring it in now and it is working great! Jmayes

Hi all, The MIOS32 tool chain setup page implies the SVN needs copied to the local drive, I can't seem to find a way to do that. Is there a download link somewhere I am missing? From; http://www.midibox.org/dokuwiki/doku.php?id=windows_mios32_toolchain_core "DOS: (we assume, that the repository has been downloaded to D:\) set MIOS32_PATH=/D/mios32/trunk" Can someone clarify that for me, Thankx again, Jmayes

Thankx again TK! Yes, I was just coming to the realization that the o'l mios8 programs would not load into mios32 but from what I have figured out so far the routines I have already made will work with little modification. The most help I will need will be to get it configured for the high speed transfers. I have ordered a few from SmashTV to play with and I will look up the info you supplied. Hopefully by the time they arrive I will have a battle plan. Thankx again! Jmayes

Hi, I think I have good news. I have achieved a 64x4 matrix scan using the dio128, it also gives you the normal 128 outputs and 8 analog in's. I am using the Acont pins to mux the keyboard buss's and 2 dinx4 modules wired across the keys. Each matrix level outputs on the next channel up. I plan on publishing the project in the next few days. Hopefully that will help, Jmayes

Hello all, I too am doing a Pipe organ and needed the SAMS to be controlled via midibox and I think I have came up with exactly what the OP John_C was asking for (as well as others). I modified the ain64_din128_dout128_v2c example application in C to flip the Dout pins off after 500ms AND I added CC81/80 functions so my SAM system would be compatible with Johnh's scheme, I believe Trevor is using that scheme as well. Here is how it works; Everything is on midi Channel 1 SAM Drivers (Dout's) Pin 1 is for Stop#1 ON, Pin 65 is for Stop#1 Off, 2&66 are Stop 2, 3&67 are Stop 3, etc. Send "Note 1 on" and pin 1 will go high for 500ms, if you send a "note 1 off" before the 500ms is up it will lower the pin early. Notes 1-128 correspond to pins 1-128 which is pretty straight forward. 1-64 are Stop on's, 65-128 are Stop off's (Hauptwerk Scheme) Now you can also send a Controller CC81 and data value of 1 and get the same pin 1 to go high for 500ms (Stop 1 on) Send CC80, Data value 1 and pin 64 will go high for 500ms (Stop 1 off) Data Values of 1-64 correspond to Stops 1-64 (Johnh's Scheme) Switch Inputs (Din's) I pretty much did the reverse for the switches. by toggling a Din high it will send a "Note on" (0x90/Pin#/Vel 0x7f) AND a CC81 w/pin# as the value. When the same Din toggles back Low a "Note off" (0x90/Pin#/Vel 0x00) AND a CC80 w/pin# as the value. Also when a Din goes low a "Note on" is sent 64 notes higher to create a SAM off Note on's and note off's between the natural note and the note 64 higher are handled with reverse polarity. So when Din 1 goes high a "note 1 on" is sent and a "note 65 off" is sent as well as the CC described above Likewise when Din 1 goes low a "note 1 off" is sent and a "note 65 on" is sent. Basically my program does both schemes of operation (note on's and CC81/80) at the same time so you can send or receive either and your SAMS will operate :) If you connect midi out to midi in on the same midibox you will see the Din's pins operate the correct Dout pins as described above. All the fun stuff is in main.c, if you need to change the channel or enable/disable some of the functions you can do it there. I tried to comment everything well and actually my code is not very long, most of it is still original. My skills at C are not very good either so I am sure the routines can be further optimized and of course there may be bugs but I hope not ;) Oh, Did I mention that the 8 analog inputs are still available and active, great for Swell pedals! The File package has a HEX that is ready for midi-box upload as well as my modified main.c I am also including JohnH's CC81/80 stop list for a reference to follow, Trevor please confirm if you are using the same list. Hope this helps someone! Jmayes JM8180-Final1.zip

Thank you TK for the fast concise answer. I guess it's time for me to invest in a few MIOS32 cores to continue on my quest. Will I be able to use the C app I have already written and just dink with the DMA settings or will it require some work in the root mios asm? Thankx again! Jmayes

Hi all, I am currently working on a matrix scan system using the DIO128 w/64analog example application. I have it working fine at 1ms intervals but to match the scan system of my organ I need it to operate at 10us, that is I need to shift the first 64 bits of the SIO within that amount of time, I can then wait 10us between scans. Can it be done? MIOS32 perhaps? Please someone let me know if it is at least possible so I can decide if I need to go back to plan-b. Thankx all, jmayes

Sounds like a good idea to me, the spot where the ABCD lights were is ideal for a 2 line LCD display. While the MDIO128 supports a display you can not do custom messages without any custom coding (I don't think). They do have a LCD message app but you will need another core for that. Good luck! Jmayes

As far as I know that is a limitation of the MDIO128 app, unless your going to do your own coding you will need two cores. No real reason to go with the 32 for what your doing, the core8 will work nicely and is less expensive. Jmayes

I was hoping that someone could point me to the test diode matrix scan routines TK made. The old links are no longer good. Sorry if my above post was too wordy, was just thinking out load. Thankx again all, Jmayes

We should keep this project here, I have another organ I need help with the diode question. You have what you need, you are going to wire all your keys and stops one at a time to the Din's which will be straight forward. One note, you will need 2 cores to drive 7 Din's (each core can have up to 4). Good Luck! Jmayes

I don't need but a few continues controllers for my project so if I can disable all but one pot on each analog input, 4051's will not be needed. I looked over Serges GUI but did not see a disable in the list Hack the syx file? Thankx for the help, Jmayes

What ever came of this project? Are the test files TK made posted anywhere currently? And was there ever a x64 matrix config made (4x64 or 8x64). The reason I ask is that most of the older Rodgers organs (I believe the Trio included) have a scanning system that scan's the whole keyboard at once, each of the keyboards are diode matrix-ed so that all the C1 keys, C#1 keys, D1, keys, etc of all keyboards and pedals are wired together and the keyboard buss-bar contains the scanning pulse. A simple async ring counter is used to drive the scan pulses. The Generator diode keyer matrix is also provided the same keyboard scan pulses so they knew which sounds to put on which keyboards. Couplers in this system were free, all they (Rodgers) had to do was muk with the scan pulses a bit to make any keyboard play sounds from any division. Now that aside, IF the Midibox did scan 64 at a time it would encompass a whole keyboard (61 notes) and I could disable the old async scan generator and use the scan pulse from the Midibox instead. Going a step further if I were to assign the generator matrix a different set of scan pulses (from another midibox doing the same DO functions in reverse) the keyboards and generators could effectively be separated. WITHOUT un-wiring anything! If this could be pulled off then only 1 chain of DI's and one chain of DO's would be needed to midi-fi most of the older 70's & 80's Rodgers organs and enable midi to be used alongside the old electronics or in-between the keyboards and old generators with out having to do any buss wiring changes. I used to service these models and know them inside and out, I can do any hardware design needed and provide documentation and schematics but my firmware skills are limited. I would love to see someone jump in and help on the asm side of things. Jim, do you still want to do your Trio? Midibox is great stuff! Jmayes

I think it was the +14v that went to the bulbs but it's been a long time. Not having to contend with the negative voltage keyers will make life much easier for midifying you should have it going no time. Driving the amps directly will require a healthy signal, I think they take 2-3v for full output, the headphone output of your computer should do nicely. I hope you did not loose that Leslie! Good luck, Jmayes