Larry Standage

Members
  • Content Count

    36
  • Joined

  • Last visited

  • Days Won

    2

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. I'm not aware of a GUI offhand, but I did find this download that is supposed to be a front end for pic32prog. Haven't tried it myself. https://www.rictech.nz/pages/8/Downloads
  2. I don't know if there is a bootloader specifically for the MAX32 that goes through the physical USB, rather than the USB-to-UART chip. However, there are some USB based bootloaders for other boards available. https://github.com/chipKIT32/chipKIT-digiboot On that one, look for 32MX7 USB hex files. The LEDs probably won't work, but you should be able to communicate through USB. https://github.com/chipKIT32/PIC32-avrdude-bootloader This one has a bootloader project, so you could build one specifically for the MAX32 via USB. But there are hex files for the Fubarino SD, and the UBW_MX795_USB.hex that might work.
  3. Sorry, I misread your original question. There is pic32prog, which can communicate with the chipKIT bootloader on the MAX32 to load applications. https://github.com/sergev/pic32prog
  4. You have to use an external tool, such as PICkit 3, PICkit 4, Snap, ICD 3, ICD 4, or Digilent PGM. These can be used with the MPLAB X IDE to load the bootloader and program it.
  5. It also depends on what you need to be able to do. If you're needing to debug your code, the only option are those mentioned. The Snap debugger is a very inexpensive option ($15, and discounts are pretty regular). If you don't need to debug, you would have to use a linker script to make the program look like something the MPIDE or Arduino IDE produces, but then you have to be able to download it through the bootloader.
  6. 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!
  7. 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 (https://www.uecide.org) PlatformIO (https://platformio.org) Arduino IDE with either: the Digilent Core (https://reference.digilentinc.com/learn/software/tutorials/digilent-core-install/start) the chipKIT Core (https://chipkit.net/wiki/index.php?title=ChipKIT_core)
  8. 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.
  9. 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.
  10. 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.
  11. The source code for all of the bootloaders is available on GitHub. https://github.com/chipKIT32/chipKIT-digiboot
  12. The sources for the bootloaders on the Digilent boards is available at this GitHub repo: https://github.com/chipKIT32/chipKIT-digiboot
  13. The MX130 does not have USB, which is what the DP32 bootloader would require. Are you planning to go through a different Interface?
  14. 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.
  15. 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.