Search the Community
Showing results for tags 'pro mx7'.
Found 3 results
I'm pretty confident I am following instructions to the letter but it's possible I am doing something wrong. But any assistance here would be great. MPLab X (5.20), XC32 (2.10), Arduino 1.8.10, Chipkit Library 2.10, Importer 1.0.6 (All the latest), Target Board is Pro MX 7. The latest importer states these versions should be acceptable because of the whole "or later" caveat. I've added photos showing I'm my directories (pretty sure they're all pointing to the correct location I'm trying to upload the Chipkit Wire - Master Reader .ino file. I select the Pro MX 7 in Arduino IDE, open the sketch, and save it to a different folder. Is that possibly the wrong step? Just spit balling. Is there some grand secret to making this work that I don't know and the internet refuses to tell us? Here's what that last photo says: java.lang.RuntimeException: java.lang.NullPointerException at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess(ArduinoBuilderRunner.java:109) at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess(ArduinoBuilderRunner.java:84) at com.microchip.mplab.nbide.embedded.chipkit.importer.ChipKitProjectImporter.preprocessSourceProject(ChipKitProjectImporter.java:307) at com.microchip.mplab.nbide.embedded.chipkit.importer.ChipKitProjectImporter.execute(ChipKitProjectImporter.java:174) at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.importChipKitProjectFiles(ImportWorker.java:275) at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.createProjectFromChipKit(ImportWorker.java:189) at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.invokeImporterTasks(ImportWorker.java:144) at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.doInBackground(ImportWorker.java:94) at com.microchip.mplab.nbide.embedded.chipkit.wizard.ImportWorker.doInBackground(ImportWorker.java:72) at javax.swing.SwingWorker$1.call(SwingWorker.java:295) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at javax.swing.SwingWorker.run(SwingWorker.java:334) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NullPointerException at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.lambda$findMainLibraryPaths$0(ArduinoBuilderRunner.java:191) at java.lang.Iterable.forEach(Iterable.java:75) at java.util.Collections$UnmodifiableCollection.forEach(Collections.java:1080) at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.findMainLibraryPaths(ArduinoBuilderRunner.java:186) at com.microchip.mplab.nbide.embedded.chipkit.importer.ArduinoBuilderRunner.preprocess(ArduinoBuilderRunner.java:99) ... 14 more
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!
Greetings! I have an Pro MX7 that I want to use as a development platform for a project and have a question on performance differences between MPIDE and MPLAB X. From what I understand, MPIDE is an Arduino-like environment that works with a lot of Arduino libraries. I like the sound of that because it could make things "easier" to just use a library than create it all myself and Arduino seems to be the "go to" platform for hobbyists. However, I wonder if MPIDE suffers from poorer performance than I'd get trying to do the same thing in MPLAB. A classic example with arduino being digitalwrite() being "expensive" in terms of performance versus directly working with the I/O port. But there are more direct ways right? I've tried messing with MPLAB Harmony, which has libraries to cover most things I need, but to be honest I'm finding it a big confusing. I also don't know if they'd be any better/worse than arduino libraries? The project I'm wanting to tackle is a complex one (at least for me) although on the MCU side it isn't too complex. It's a pinball machine. So, in essence it has to do the following: Play background music Play sound effects mixed with the music/other effects Display animated graphics on a 128x32 dot matrix display (these need constantly refreshed at ~70Hz like a video interface, they do not store a 'frame' locally) Read all the above from a microSD card Control an LED matrix, probably at least two shift registers for 8x8 = up to 64 LEDs Read from a switch matrix, again probably 8x8 = up to 64 switches Control open drain FETs for solenoids (probably again via shift registers). Around 10-12 or so. However, I'm toying with the idea of using PWM to control the power of solenoids. The first 3 I worry about consuming a lot of cycles because switch closures for #6 can not be missed. So my question is, would using MPIDE be viable, or do I need to work at a lower level to get enough performance? Is it doomed regardless and a second MCU would be needed to handle the A/V functions?