Larry Standage

Members
  • Content count

    24
  • Joined

  • Last visited

  • Days Won

    1

Larry Standage last won the day on May 16

Larry Standage had the most liked content!

About Larry Standage

  • Rank
    Member
  1. The MX130 does not have USB, which is what the DP32 bootloader would require. Are you planning to go through a different Interface?
  2. Using Segger J-Link Against chipKIT Boards

    Yes, I have done it, and it does work really well. One big advantage is that it doesn't take up Flash space with a debug executive the way the Microchip tools do. It's also quite fast. Once it has been programmed, it can only update the flash pages that change between execution, reducing programming time. But, every once in a while, I can't get mine to connect. When that happens, I usually find I have to chip erase the part with MPLAB tools, then try it again.
  3. PMOD connector spacing

    Here is the relevant phrase from the PMOD Specification document: "When multiple connectors are placed side-by-side along a board edge (either host or peripheral), the connectors are spaced 0.9”, center-to-center. This allows for 0.8” wide modules to be plugged side-by-side into a host without interference. Peripheral modules with multiple connectors must also have them spaced on 0.9” centers for direct connection to a host." .9" is 22.86mm, so it looks like you have it correct.
  4. ChipKit CMOD watchdog & lockup

    If the part is not in sleep, then the watchdog will reset the part. That leaves the question of whether you could put the part to sleep during that time.
  5. Analog and Network Shields with Max32 at the same time

    They should be. A lot depends on the kind of Analog Shield, whether it outputs 5V signals or only up to 3.3V, and what pins it uses that might be in use on the Network Shield. You should check the schematics and verify that there are no pins used by both.
  6. Evaluating Fubarino SD

    The Fubarino bootloader is primarily used over the USB interface on the board. So upgrades in the field would not be able to support that capability without changing the bootloader itself. The source code is available for it, however. If you're only interested in keeping the existing bootloader, but debug using ICD3, then what you will probably need to do is to download the hex file of the bootloader, and add it as a loadable in the MPLAB X project. Then the two will be put together at compile time, downloaded at the same time, and then you should be good to go.
  7. uC32 communication with PC

    If the USB to UART speeds are too low, another option would be something like the MCP2210, which communicates over SPI, and should go much faster.
  8. Connected uC Lab problems with Debug

    That particular option was removed from the EF series, so you can just delete the line. It doesn't do anything on the MZ EC anyway.
  9. Connected uC Lab problems with Debug

    This message is coming up because your specific Wi-FIRE board has a MZ EF part instead of the MZ EC part expected by the project. You should be able to change the processor in the project to the PIC32MZ2048EFG100, and give it a try again.
  10. Those are pin names/functions for the PIC32 part on the MAX32. Look at the data sheet for that particular device. It can be downloaded here: http://www.microchip.com/mymicrochip/filehandler.aspx?ddocname=en545749
  11. Uc32 J7 resistors

    btb4198: Where are you measuring 4V? You say 4V, but you don't indicate if that is across the resistor or some other point in the net. 0.8V makes sense if you are measuring across the resistor. But if you are measuring somewhere else, then it depends on your port settings, state, etc.
  12. A couple things come to mind. Is anything else using that pin for something? Check the RPB14R register to make sure it's set to 0000. Otherwise a peripheral might be driving it. The other question is whether you have the CVREF module turned on. If so, that function takes higher priority than the PPS functions (which is why it is first on the list of pins).