Jump to content

Rio

Members
  • Content Count

    676
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by Rio

  1. I remember, 500mA was minimum for 1 core 1 Sid.
  2. 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.
  3. 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
  4. but if you read further below, you can see that the problem was with the cable again!
  5. 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
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. and did you install LPC11U35 installer before and restart PC?
  11. Ok, i have found my rev.D1 board again and plugged it in. It's using CMSIS DAP linker too. Yes, it is also not found (with closed jumper). So something is still fishy. Have you ever tried to load the host drivers from nxp: https://www.nxp.com/design/microcontrollers-developer-resources/lpc-microcontroller-utilities/lpcxpresso-board-for-lpc1769-with-cmsis-dap-probe:OM13085 at the bottom: Host Device Drivers ( 1 ) - Firmware and drivers for LPC11U35 debug probes I think that's for it ..
  12. did you try this: If his guidance on the rev D doesn't help, you could PM him. at least he managed it. Edit: Oh, I just checked again at myself: I had actually successfully flashed a Rev D1 via the IDE 8.2.2 in the past. I can't remember any unusual things now.
  13. rev D should work: I'm not sure what else to do ... but maybe try another PC. After that you can find out what's going on with the current one.
  14. In some posts, people get in trouble with CMSIS-DAP. but take a look here: https://community.nxp.com/t5/LPC-Microcontrollers/LPCXpresso-LPC1769-board-not-recognized-when-debugging-with-LPC/td-p/1200156 On the other hand, I read that it probably also worked with 8.2.2 ... I can't test it myself (i have only rev.A B C). Do you have the chance to grab an older revision? Don't you want to go to the newer CPU sooner if that is so much trouble? But you could still do some research ... it's up to something.
  15. try again from the beginning. should normally go now (reboot, reinstall, reconnect etc.) otherwise something went wrong .. or the linker type isn’t supported by 8.2.2 ?? I will take a look later.
  16. Rev D2 - JP3 Open - normal Boot, Closed DFU LPC link Boot. https://www.nxp.com/docs/en/supporting-information/LPCXPRESSO-V2-BOARD-FAMILY-SI.pdf you should close it for LPC link mode. that should be the 3.3V connection to the linker, which then gets priority when booting.
  17. Which revision are you using? I think the new boards were put into dev mode by a jumper. But give me more details - pic or number of jumper.
  18. should work.... pls use LPCXpresso IDE v8.2.2. Otherwise try another usb port, please deinstall lpc/nxp drivers and reboot/reconnect. Have you activate the computer (or register with nxp)?
  19. Which OS do you use? as soon as the USB cable is plugged in, additional LPC drivers etc. are installed(automatically). You have to allow that and wait a little.
  20. guck mal, an der Mixerschaltung liegt es nicht. Danke erstmal für die Infos. In den Videos geht es aber mehr um die Beseitigung von Störsignale (Mhz), statt Humming - sehe ich das richtig?
  21. Good question, I don't always want to lift the SIDs out of the C64 socket to do configurations or even possible future firmware update for the ARMSID. but I can hardly imagine it because there is a simple protocol behind it.
  22. ja ok danke für die info. Ich denke mal die Ursache müsste aber in der schematic zu beseitigen sein. Anderseits kostet der kern nicht die welt, kann ich ja mal mitordern bei einer Bestellung.
  23. Bug when recording inside track with Quantize: If you record notes with e.g. Quantize (e.g. 80%) and meanwhile/afterwards CCs or aftertouch (channel pressure) are being sent while a note is held, the length of the recorded held note is immediately interrupted. Would be really cool if that was fixed. Thank you. Best regards, rio
  24. Das verstehe ich nicht - wie das funktioniert, und ich hab so einen auch nicht zur Hand. Hat sowas bei dir mal geholfen? Und ich verstehe leider auch nicht, wieso ich nur ein Brummen drauf hab und andere anscheinend nicht.
  25. The DFxx address is only related to the address range of the C64, not to the real PIN Out.
×
×
  • Create New...