Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Rio last won the day on April 15

Rio had the most liked content!

Community Reputation

8 Neutral

About Rio

  • Rank
    MIDIbox Guru
  • Birthday 04/26/1978

Profile Information

  • Gender
    Not Telling
  • Location
  • Interests
    Music, 8Bit, Synths

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. 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
  3. 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 vi
  4. First of all, ask modular addict whether there are any new ones
  5. hi, 3) use PC messages, not CCs. 4) right - you have 1 stereo pair. (you can stuff up to 8 sids by 4 cores), but i am not sure how many cores can be loaded in sammichSID because I am not familar with sammich board. 5) pls use the "mios studio" software. and yes first upload the newer bootloader MIOS and then the application. Everything can be uploaded via midi, but take care about the core IDs and the correct bootloader MIOS file. MBSID V2.044 changelog: Please update to MIOS V1.9h before uploading the application, otherwise the improvements won't be effective. have f
  6. I remember, 500mA was minimum for 1 core 1 Sid.
  7. just check all contacts. maybe the PIC is not firmly in place, midi port connections may become loose over time. it could also be cold solder joints. take a close look at the hardware.
  8. short and thick... and if that doesn't help, we'll try to update the firmware of the probe. ps: don‘t forget to remove the jumper of JP3
  9. but if you read further below, you can see that the problem was with the cable again!
  10. ok, i have now tested a different usb cable (the cable is short and thicker - it looks more stable). Everything works now (also with win7 and win10). The jumper must be removed, otherwise the linker will not work. no mbed driver needed or anything else...it worked for me without installing anything or without updating the firmware now. but i'm not sure if i ever installed the mbed stuff before i was switching to win10 - that was 2 years ago, but I don’t think so, because I restore a untouched/clean OS once a year. so either you actually don't have a really good short
  11. ok i tried the same steps that you mentioned. And I come to the same conclusion that it does not work under win10 as you described (with me, however, no drivers are shown in the device manager). I don't quite get it - I'm (actually) sure I got it installed in the past - but that was a win7. But when I try to install it in Win7 it doesn't work either. When installing the mbed driver, the same error message appears. it is really crap right now ... maybe gerald.wert has an idea, he also successfully connected it, just didn't write how.
  12. there are 3 more links at the bottom by ZhangJennie, about that post about 1769 rev.D problems, referred to: - MBED serial driver - probe firmware - Can't find debug Probe ticket.. I know the picture you posted/shown is related to a lpc8xx but I think it uses the same probe (CMSIS-DAP). BTW: You have to think of it this way: there are two boards - on the one hand it is the debug / linker probe and on the other hand the LPC1769 board - both are connected. If the jumper is set, the probe has priority.
  13. The board isn't different...LPC11U35 is the CMSIS-DAP Debug Probe board name, or not? and it is referred to by the LPC1769 board rev.D on that side.
  14. i found this too: https://community.nxp.com/t5/MCUXpresso-IDE/OM13085-Board-No-compatible-emulators-available/m-p/1026193 did you follow these instructions?: https://community.nxp.com/t5/LPC-Microcontrollers-Knowledge/Flashing-and-Installing-the-new-firmware-and-drivers-for/ta-p/1127375 I know tired but it should work at some point.
  15. and did you install LPC11U35 installer before and restart PC?
  • Create New...