jfrenzel

Members
  • Content Count

    30
  • Joined

  • Last visited

  • Days Won

    1

jfrenzel last won the day on May 31 2017

jfrenzel had the most liked content!

About jfrenzel

  • Rank
    Frequent Visitor

Recent Profile Visitors

1522 profile views
  1. 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!
  2. 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. Just a thought ... CAN Workspace.dwf3work
  3. 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?
  4. 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 schematic and reference manual, it appears that I can't directly connect to RX and TX for either CAN1 or CAN2. However, it appears that if I short together all of three pins of JP1 and all three pins of JP2, then the RX and TX of CAN1 will be available on pins 1 and 4 of connector JF. As far as I can tell, shorting all three pins together will not create an electrical short, as nothing on the board is driving the outside pins of JP1 and JP2. (2) Is this correct? Thanks!
  5. 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.
  6. 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?
  7. 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. :-)
  8. 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
  9. 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 ...
  10. 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?
  11. 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
  12. 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!