jfrenzel

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    1

jfrenzel last won the day on May 31 2017

jfrenzel had the most liked content!

About jfrenzel

  • Rank
    Member

Recent Profile Visitors

1281 profile views
  1. Thanks Jon. What's the difference between the Microchip MAL and the Digilent libraries mentioned on p. 14 of the Reference Manual? The Microchip Applications Library, MAL, available on the Microchip web site contains USB driver code for implementing either USB host devices or USB function devices. This library contains numerous examples demonstrating both device and host operation of PIC32 microcontrollers. With minor modification or configuration, these reference designs are suitable to use for developing USB firmware for the DigilentPro MX7 board. Digilent has USB libraries available that can be used to develop both USB device and USB host applications when using the board with the MPIDE development environment. These libraries are built on a custom version of the Microchip Applications Library and can be downloaded from the Digilent Pro MX7 product page on the Digilent web site.
  2. I have an old Cerebot MX7ck board that should be identical to the current Pro MX7 board. The PDF documentation for my board mentions that Digilent has USB libraries that can be used to develop both USB device and USB host applications, built upon a custom version of the Microchip Applications Library, and that they can be downloaded from the product page on the Digilent web site. However, the Resource Center page for the Pro MX7 only has two tutorials, neither of which looks appropriate. Are these libraries somewhere on GitHub?
  3. I am playing around with the SDWriteREAD example sketch under DSDVOL that is part of the Digilent core and I'm wondering if there is any documentation available, other than the source code. (I happen to be running Arduino 1.8.2 on a Wi-FIRE, but that's not relevant. :-)
  4. I repeated the whole flow after creating a D:\ardo folder and two subfolders D:\ardo\build and D:\ardo\mplab. I then changed my Arduino preferences.txt file to set the Arduino build directory and followed the steps on the attached PDF. (Namely, import the ELF and add the Wi-FIRE bootloader under "Loadables" project folder.) I was then able to set breakpoints, single-step etc. Success! Debug Arduino sketch using MPLAB-X.pdf
  5. It appears that the problem was spaces in the path to the MPLAB-X project directory. I think I solved the problem by copying the entire Arduino build tree from the Temp folder under a user's AppData tree (Windows 7) to a short path with no spaces or caps. (The joy of legacy Unix code under Windoze?) I'll repeat the whole painful process after the weekend and post the final outcome. I did once have a student try to convince me that spaces in a build path weren't really a problem, but I have never trusted it. Just call me old school. Stay tuned ...
  6. I want to debug my Arduino sketch using MPLAB-X (ver 3.61) and after running into a dead end with loading the ELF file, I decided to try my hand at importing the sketch using the MPLAB plugin - "chipKIT Import Plugin (ver 1.0.4) Note: I am using the Digilent Core with the Wi-FIRE board (rev C), not the chipKIT core from chipkit.net. Attached are two screenshots. The first is the Plugin description and the second is the Project setup box. With respect to the latter, I'm encountering two problems: (1) It doesn't like my Core location, even though that is the folder where platform.txt is located; and (2) my target board pull down list is empty, although it's possible this problem would go away if (1) was solved. Any thoughts?
  7. I have an Arduino sketch that runs beautifully on a Wi-FIRE Rev C board using the chipkit wifire(Rev C) board that was installed as part of the Digilent core linked on this page https://reference.digilentinc.com/learn/software/tutorials/digilent-core-install/start NOT the chipKIT core identified on chipkit.net page. I created an ELF file of the sketch by building it under Arduino 1.8.2 (NOT MPIDE) with compiler optimization set to zero so that all of my source lines would be preserved, and the -g option. I then fired up MPLAB-X (v 3.61), imported the ELF file and added the the chipKIT bootloader image under the project "Loadables" sources. I can then run the program fine under Debug and even set breakpoints within main.cpp, but I can't set any breakpoints within my sketch code (DSPI_Demo.ino.cpp. Before hitting the "Debug" button in MPLAB-X the BP is fine, but afterwards it is broken. The attached images show some of my sources and the BP behavior. Any thoughts
  8. I am trying to come up to speed on the Wi-FIRE board and noticed that there is are two examples under the DSPI library that is included as part of the ChipKIT core hosted on the github site compared to the Digilent Core that is referenced on this page: https://reference.digilentinc.com/learn/software/tutorials/digilent-core-install/start Is there a particular reason why the DSPI_Demo sketch was not included in the Digilent core, but is part of the ChipKIT core. (Also makes me wonder what other differences may be lurking, left to be discovered.) It would appear that the two cores have not been kept "in sync". To make things even more confusing, there is also a Digilent core on GitHub!
  9. I have since discovered that there are two relevant libraries for Arduino included as part of the Digilent Core: DSPI and DSDVOL. I believe the former provides a hardware implementation of SPI using the PIC32 SPI controllers, which is in turn used by the latter to implement access to the SD card via SPI3.
  10. I've been looking over the SD library that was installed as part of the chipKIT boards (ver 1.4.1) and I get the distinct impression that it implements the SPI protocol to the SD card using bit-banging, rather than a PIC32 SPI peripheral. Is this correct? Assuming so, are there any Arduino-compatible libraries for the Wi-FIRE that utilized the SPI peripherals? Assuming not, is my best be to go with MPLAB Harmony? (I'm an old MPLAB-X guy using version 2.10 and an old peripheral library)
  11. Isn't the Digilent link above to an older version of the chipKIT boards? I installed version 1.4.1 by following the instructions on chipkit.net.
  12. You got it Larry - thanks! (I may have to put you on speed dial.) :-)
  13. I have a Wi-FIRE rev C board that I would like to program from the Arduino IDE. According to the ChipKIT wiki, the ChipKIT core has replaced the need for MPIDE. I hooked up the Wi-FIRE to the UART mini-USB on the top of the board (Call out 26 in the ref manual) and then tried to program from the Arduino IDE by selecting "Sketch > Upload" but I get an the following error Programmer for Microchip PIC32 microcontrollers, Version 2.1.24 No target found. Copyright: (C) 2011-2015 Serge Vakulenko An error occurred while uploading the sketch My guess is that I need to use my chipKIT PGM programmer, but the Wi-FIRE ref manual does not discuss how to connect this. For example, JP3 and JP4 are not mentioned in the manual at all. (They are two, six pin staggered holes, one of which is labeled "JTAG"). It doesn't help that the PGM doesn't have much room to make a connection with all of the other stuff on the top of the board. Am I missing something obvious? UPDATE: I needed to change the selected COM port under "Tools" in the Arduino IDE. (Stumbled across Figure 9 here https://learn.digilentinc.com/Module/103?position=0