Larry Standage

  • Content Count

  • Joined

  • Last visited

  • Days Won


Larry Standage last won the day on July 11

Larry Standage had the most liked content!

About Larry Standage

  • Rank
    Frequent Visitor

Recent Profile Visitors

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

  1. Hi everyone, I know that, in order to use the FTDI chip as a JTAG programmer, that one of the pins on the FTDI has to be configured to allow the connection to the part. For UrJTAG, how does one change the state of the pins on the FTDI chip? Thanks!
  2. The PICkit 3 (or PKOB on Pro MX7) can only be used, in general, with MPLAB and MPLAB X. The Pro MX7 has a number of options: MPIDE UECIDE ( PlatformIO ( Arduino IDE with either: the Digilent Core ( the chipKIT Core (
  3. If you want to set both pins at the same time, rather than in two separate statements, you could also do this: LATGSET = (1 << 15) | (1 << 6); // or 0b1000000001000000 These parts have registers that can do an atomic set/clear/invert, so that you don't have to do a read/modify/write of the register.
  4. If you're looking for a way to both inject SPI/I2C data, as well as capture traffic, then the Aardvark is probably the way to go. But they do have speed limitations (800 kHz for I2C, 4 MHz for SPI). If you only need something to capture/analyze the traffic, then the Saleae tools are quite good at that, along with many other protocols. They can also capture analog data, up to 10 MS/s on the base Logic 8 unit.
  5. J1 is the correct port to use for the COM port. Make sure the USB cable you're using is both data and power. I've seen cables that are power only, and that would prevent the PC from seeing it.
  6. The source code for all of the bootloaders is available on GitHub.
  7. The sources for the bootloaders on the Digilent boards is available at this GitHub repo:
  8. The MX130 does not have USB, which is what the DP32 bootloader would require. Are you planning to go through a different Interface?
  9. I did it once when I was creating the demos in Harmony, but I don't remember all the details at the moment. It seems like there was a separate MPLAB X project (non-Harmony) that I had to adapt to using the WF32's pinout. I'll track it down and see if I can turn it into a sketch.
  10. One of the staggered 6-pin connectors that isn't populated controls the programming of the on-board debugger. Pin 1 would be MCLR, and if that is grounded, perhaps that would help.
  11. That is correct. The plugin was designed with the chipKIT-core in mind, and when it checks the platform.txt file, it is looking for the line "name=chipkit". Changing it in the Digilent core is not sufficient, however. I've found that running the plugin that way results in a Java exception, probably connected to the name of the board being different "chipKIT WiFire(Rev C)" vs. "chipKIT WiFire". The plugin takes the name and matches it with the bootloader, so you don't have to manually add it to the project. Will the sketch compile with the chipKIT-core? If so, it might be easier to try it that way, bring it into MPLAB X, and then replace the library files with the ones from the Digilent core, if that is the important part.
  12. The chipKIT PGM (or PICkit 3 or ICD 3 or Real ICE) are used only if you are trying to program through the MPLAB X IDE, rather than the Arduino IDE. Given the output, it looks like pic32prog wasn't told what serial port to look at. Did you select a port after choosing the board?
  13. Yes, the "chipKIT wifire" is the correct choice. The 80MHz version is one that isn't used, and the other one was the early boards with the ECG part instead of EFG.
  14. If you can get the demo code up and compiling on Arduino, there is now a sketch importer plugin that will allow you to run/debug it in MPLAB X.