Created Sun, 02 Jun 2013 21:25:03 +0000 by ricklon
Sun, 02 Jun 2013 21:25:03 +0000
Release Candidate 1 20130601
Changes: Updated SD Examples Support for Olimex Pinguino Boards Added processors MX150-D, 250-B, 695-L/H to avrdude.conf Added variants for WF32 and DP32 and updated SD chipSelect for share SPI2 INT1
Latest status: https://github.com/chipKIT32/chipKIT32-MAX/issues
Windows http://chipkit.s3.amazonaws.com/builds/mpide-0023-windows-20130602-test.zip Mac OS X http://chipkit.s3.amazonaws.com/builds/mpide-0023-macosx-20130602-test.dmg Linux32 http://chipkit.s3.amazonaws.com/builds/mpide-0023-linux-20130602-test.tgz
Tue, 04 Jun 2013 10:45:49 +0000
..Added variants for WF32 and DP32 and updated SD chipSelect for share SPI2 INT1..
Is there any way that we can define the SPI pins so that they do not use either Chipkit Pin 17 or Chipkit Pin 18 on the DP32? the current configuration rules out the use of the RTC module if you are using either SPI Module.
SPI and RTC need to work hand in hand for applications such as data logging.
Just a thought whilst still in pre release.
Tue, 04 Jun 2013 13:26:29 +0000
I believe you can use PPS to switch which pins the SPI peripheral is mapped to. I'm starting work on a PPS page here : [url]https://github.com/fubarino/fubarino.github.com/wiki/Fubarino-Mini-pps[/url] and although it's not anywhere near complete, it might be enough to get you started.
Tue, 04 Jun 2013 14:20:31 +0000
Your PPS page is indeed useful, thanks.
You say "On boot, the only things we map are the UARTs - the SPI pins, output compares, input captures, etc. all alone. So users will need to do mapPps() before they can use any of that."
Is that true for the DP32 as well as the fubarino ? If so then my request is not needed.
My main concern was for any default mappings made by the Bootloader.
I was also interested to see that PPS has the capability to do 1:x concurrent associations, I must play with that in mplab and see what I get, not that I can think of any practical use off hand.
Tue, 04 Jun 2013 16:29:45 +0000
I'm very certain that the bootloader doesn't set up or change any PPS mappings.
However, the Arduino 'core' startup code may (will) do some PPS mappings (for example, for the UARTs) after the bootloader has run. I don't know what Keith has put in the DP32 varient files - you can always check if you want, all the source is there - but I think there is not any other mapping being done at present.
It is our intention to get 'default' pins set up through PPS for all useful peripherals in the Arduino 'core' startup code (as defined in the varient files), but that's not done yet.
Thu, 20 Jun 2013 21:09:58 +0000
I have built on Brian's concept in the wiki entry about PPS on the chipKIT Fubarinoâ„¢Mini and created a table of function codes and available ChipKIT PIN#s for each function. I then followed it up with a practical example of outputting a reference clock.
It is based on my ChipKIT BB32 a breadboard implementation of the ChipKIT DP32, so I am not sure how relevent it is to the chipKIT Fubarinoâ„¢Mini, but please feel free to use it, modify it and do as you wish with it for your wiki.
It can be found on my blog here: [url]http://caroper.blogspot.com/2013/06/peripheral-pin-select-pps.html[/url]
Thu, 20 Jun 2013 22:54:40 +0000
Chris, if you have the time, I'd be honored if you would be willing to update the Fubarino Mini Wiki page about PPS with the information you've collected. We need more solid information on that page, as more and more people are using Minis and DP32s now and need this info at their fingertips. Thanks SO much for what you've done so far.