jfrenzel

Members
  • Content Count

    33
  • Joined

  • Last visited

About jfrenzel

  • Rank
    Frequent Visitor

Recent Profile Visitors

2102 profile views
  1. I would think this would be obvious, but the documentation doesn't go into much detail. We develop MPLAB projects for the PIC32 under FreeRTOS using the xc32-gcc compiler. All of our projects follow a specific directory structure and use relative paths, so I would like to exclude the FreeRTOS header and source files when packaging the project, but obviously not when building the project. My question is how best to do this. I believe that the reference design that I used as a starting point created logical folders for the FreeRTOS source and then added specific files as existi
  2. I get the impression that you can do a HW/SW co-design project on the Zybo Z7 by entering the hardware design using Vivado and then exporting to Vitis for the software, similar to the pre-2019 flow. (Please let me know if that is incorrect!) Can you do the same with the original Digilent Zybo? (We have a lab full of the original boards.) Thanks! Jim
  3. I think I may be having this problem as well, although I am running Exercise 4.A out of the Zynq book, and LEDs are supposed to be lighting as well. First, how do I figure out which version of the old Zybo board I have? I was pretty sure B.3, but is there anyway to verify? (The back of my board just says "Rev B".) Second, I used this board successfully in the past with Vivado 2016.4 under Windows XP, but now that I've upgraded to Windows 10 (and reinstalled the Xilinx tools, I haven't been successful with the SDK portion of the tools. (Just programming the PL from Vivado works fine
  4. Well, I''ll be - you are absolutely correct! I was working off of a sample project from Microchip and didn't think to check whether they were forming the message correctly. (Interestingly enough, the PIC32 CAN controller doesn't care, because the bus seems to keep running.) A big (BIG) thank you for your help!
  5. Downloaded thelatest Beta (3.11.30 64-bit) and have the same problem: the Logic Analyzer triggers fine with a simple, falling edge trigger on DIO6 (RX); doesn't work with the Protocol trigger. I'll attach both my screenshot and workspace. The problem may be that you appear to be using Waveforms Protocol Analyzer tool to create the CAN message, where as I am connecting to the PIC32 CAN pins of an actually CAN bus that is sending and receiving CAN messages using the PIC32. What I'm implying is that perhaps the Waveforms Protocol Analyzer is correcting for mistakes in the Logic Analyzer.
  6. I am able to capture a CAN message using the logic analyzer with a "Simple" trigger of falling edge on the TX line (polarity low), but have not succeeded in triggering using the "Protocol" trigger. Attached is a screenshot of a transmit capture using "Simple" and the waveform looks correct. However when I use the attached "Protocol" settings, the analyzer never triggers. What am I missing?
  7. I have one of the older Cerebot boards which should be equivalent to the Diglent Pro MX7 Embedded Systems Trainer Board that is currently for sale. I would like to capture CAN traffic using an Analog Discovery module and Waveforms software. I have two basic questions. After studying related posts on this forum, I get the strong sense that Analog Discovery and Waveforms software are better suited for connecting to the "PIC side" of the transceivers (RX and TX), rather than CAN side, where CANH and CANL are differential signals. (1) Is this correct? After studying the Cerebot sche
  8. 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 availab
  9. 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?
  10. 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. :-)
  11. 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
  12. 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 ...
  13. 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;