Rio
-
Posts
727 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Blogs
Gallery
Everything posted by Rio
-
You should backup these files as long as they can be read on the PC.
-
I never said it shouldn’t be a hardware link. Maybe the right term is „debug Interface“, … …but I don’t have STM32F4 in use for my mbseq.
-
I don‘t think, that you have care about a SD card for uploading mios32 app or (in the worst case) flashing bootloader by a linker.
-
This is a standard message when the bootloader/mios32 is on. It is good that it is running. After that, you can safely upload the MBSEQ, but for the right core! - which is not quite clear here yet (probably STM32 core).. but MIOS Studio should already give you the info back with the USB midi connection. more infos here: http://www.ucapps.de/mios32_bootstrap_newbies.html and here: http://www.ucapps.de/index.html?page=mios32_bootstrap_newbies.html Mios Studio 2: http://www.ucapps.de/index.html?page=mios32_bootstrap_newbies.html
-
Please use another SD card!! Terminal output would be nice too.
-
What country are you from? Greetings, rio
-
Hi, there might be something wrong with your board. I tried it several times with my different 1769 board revisions - a,b, d - all with success. So you can check your board for bad solder points and/or the debugger/link interconnection.. maybe you missed something.
-
how can it break? as long as you haven't trotted up, it should still work.. probably the mios firmware/app on that device is corrupted, isn't it? as long as the bootloader is still there, which is in a protected area, you can fix it. And yes, you can not take a PIC18f4620 - different features, different storage area.
-
Hi, you could create a simple program, also with a PIC core board with the help of a bare skeleton available here on ucapps. the k2 speakjet project is a good example for a serial communication (max232), but for your needs IIC would be more comfortable (as long as it is supported by your speakboard). you may get faster results with an Arduino board too. With all this knowledge you can surely also hack the SEQ for your needs, but that takes quite a lot of time to understand everything that is already there. you could still allow a control via midi on your own board too. greetings
-
wasn't it the 6581 emulation that had more bang?
-
You did circuit bending.
-
but the PIC survived, right? the workhorse...
-
Ok...
-
Yes, mbsidv2 supports external filters by aout modules. I had done that in the past but then removed it again. How did you kill a swinsid??
-
BTW: Is the armsid filter section purely emulated or analog? and are the filters just as sensitive as the original (regarding electrical damage)?
-
Yes, without a doubt, I understand what you are referring to .. .. and otherwise we would hardly have dreamed of making a box with sound chips from old home computers.
-
... but SID isn‘t analog, only the DAC Part inside, right?
-
I think the term VA is not quite right, but yes it is no longer a real SID and an emulation is running. Nobody hears the difference in productions anymore. I think this is more about the aspect of using these 'retro' chips (including me) than just the pure sound. .. and of course, adequate respect should be paid to all developers who deal with the chips and their emulations.
-
I have the armsids for two main reasons: I see them as quite passable replacements in case all my SIDs break down, and with regard to the 6581, the armsid might be a better choice as I can never find suitable filter pairs with the originals can. The 8580s, on the other hand, are quite stable.
-
This is a far better option than wearing down the c64 socket or the SID that is in my beloved C64.
-
But they may replenish it (but yes possibly).
-
I'm not sure now whether your plan matches what has already been implemented with the MBSID. There are 4 sound engines, take a look here: Lead Engine Bassline Engine Drum Engine Multi Engine http://www.ucapps.de/midibox_sid_manual.html
-
Yes very good! I just wanted to make sure that the wrong thing is not accidentally uploaded, although the "MIOS Studio" already warns or maybe blocks this. Your bootloader is fine on your PIC just MIOS and the app needs to be uploaded in order. You can't screw up a lot there either. Otherwise just upload the two things again. Have fun and don't hesitate to ask :D
-
Oh my fault ... I meant MIOS. You only upload the newer MIOS version with the bootloader (which is already burned on the microchip). You don’t upload the bootloader itself!! (that's for a burner and not for midi transmission). Sorry, my confusion in the binary term - I just recognized it now. I hope you read it before trying, but however, MIOS Studio should warn you about this (range detection). from the readme.txt of mios1.9h take case A): A) you've already installed MIOS8 V1.9g, and want to update to MIOS8 V1.9h Thats the common case, you have to upload one of these files via MIDI as described on the http://www.ucapps.de/mios_bootstrap.html page depending on the PIC derivative you are using. ... PIC18F4685: -> pic18f4685\midi\mios8_v1_9h_pic18f4685.hex upload the mios1.9h hex and then you can upload the MBSIDv2 app again.
-
First of all, ask modular addict whether there are any new ones
