Hi,
I reviewed the schematics and I believe the chipKIT Pi could be used for an RTC for the Raspberry Pi. You would have to stuff the battery as you mentioned and I would also recommend stuffing the 32khz crystal which can be used to drive the RTC inside the chipKIT Pi for more accuracy.
Kim
I have been working with the chipKIT Pi for a little while now and thought I would give you a little tour of this great device and mention a few things I think it would be good for. The chipKIT Pi is based on the chipKIT boards made by Digilent. These boards are Arduino compatible. That is to say they use a similar IDE as the Arduino which is called MPIDE. You can down load this software free from Digilent.
If you aren't familiar with the Arduino IDE there are lots of places where you can get help with the environment. Here on Element 14 the The specified item was not found. area would be a good place to start. Another resource would be the Digilent site that contains a lot of interesting code examples and tutorials as well as the MPIDE software.
The chipKIT Pi communicates with the Raspberry Pi over a serial link. The chipKIT Pi uses pins P11 and P12 for the serial link from the Raspberry Pi as well as 5 volts, ground, and reset. The rest of the pins on the Raspberry Pi connector are routed to the Raspberry Pi connector on the chipKIT Pi. This gives you external access to most of the pins on the Raspberry Pi even if the chipKIT Pi is plugged in.
On top of the chipKIT Pi you have standard Arduino connectors. Not all the pins on the Arduino connector are active. The pins AREF, D7, D6, D5, D4, A2, and A3 are not connected on the chipKIT Pi. The rest of the pins are connected and function similarly to the Arduino.
You maybe saying but, what is it good for? That is a very good question. I have worked with Unix/Linux for many years and I know that sometimes the interrupt response times of these systems can be a little on the slow side. The chipKIT Pi would work very well in a situation where interrupts need quick response.
Another good use for this board would be in assisting the Raspberry Pi in a hardware intense situation like controlling the brightness of an LED or the speed of a motor. The chipKIT has two dedicated hardware PWM channels as well as RS232, I2C and SPI buses. Any of these peripherals could help your Raspberry Pi out.
There is another bonus to the chipKIT Pi. It has 3 5V tolerant pins (D12, D10, and D2) that you can access. This will save your sensitive Raspberry Pi from damage. I see in the forums over and over again warnings about the Raspberry Pi I/O not being 5V tolerant.
The PIC on the chipKIT Pi has a really fast 2 channel 10 bit ADC in it. The data sheet says that it can do 1Msps. This would make a good input for an oscilloscope.
Another thing I thought of using the chipKIT Pi for would be to handle a wireless link. The wireless link wouldn't be a WiFi link but a custom link of wireless sensors. I have been working on such a project. You can see that project at my site (http://theengineertutor.com/). I have been etching my own boards and using Eagle to design the boards. I currently have 5 nodes up and running reporting temperature from various places in my yard and house. In this case the chipKIT Pi is handling the wireless link and all of the protocol from the sensors. The Raspberry Pi only receives good packets. This can free the Raspberry Pi to do other important things.
These are just some of the things a chipKIT Pi would be good for. I'm sure there are many other uses that you can think of.
Kim
I’m kind of new to Linux but I did get the Raspian version with the MPIDE loaded and running. I put the MPIDE version of Raspian on an 8gig flash card. It looks like the version of Raspian that is loaded is somewhat nonstandard because when I run raspi-config and try to expand to use all the memory I get a message saying “your partition layout is not currently supported by this tool.” How do I expand the partition to use the entire flash memory?
Thanks
Bill
Bill,
I see what you are saying. I ran the program and got the same results as you did. I too have an 8gig card in my Raspberry Pi and I went through the install document to get the MPIDE version of the OS working. I did a "df -h" command and found that it looks like I have only used 2.5 gig of the card. I don't have an answer to this currently I think we need to hop over to the Raspberry Pi section and ask this question. I'm not new to Linux but I am new to the Raspberry Pi.
Kim
I am not new to Arduino, Chipkit, or Raspberry Pi. I did notice that the noobs distribution which includes MPIDE won't survive a rpi-upgrade to get it to use 512 RAM. It is seriously unuseably slow. I mean minutes to respond to a pull down. I presume that's because MPIDE really wants more RAM. Is that correct? If so, how have you been upgrading the distro you've been downloading?
Also, is there a practical way to load the MPIDE onto an existing OS on the PI without recompiling the universe?
Anyway, I bet I'm missing something simple, so I stand ready to learn.
I did figure out what I was doing incorrectly
I plugged the flash chip into my Ubuntu desktop system an ran gparted
I then resized /dev/sdb2 and then resized /dev/sdb6 and executed the 2 resize operations
And this changed the partition sizes
The mistake I was making was trying to resize /dev/sdb6 without changing /dev/sdb2
It ran slowly and took a while but did work.
Hope this helps other frustrated users, I don't know if you can do this on the raspberry pi.
Bill
George,
I have been looking at the same issue. I have noticed the same thing, how slow the system runs. This is my first experience with the Pi and thought that it was just a slow machine. I to have a model B with the 512meg of RAM.
I thought the same thing that if I could load the MPIDE on a system that is already configured properly it should run butter. I haven't found an MPIDE download that would run on the Pi. I'm still looking. Let me know if you find a solution.
Thanks
Kim
I suppose I would have had better luck if I had actually beeen using a 512k board..D'oh! Anyway,it only seems to be slow the first tike out. Must be setting up sketchbook or something. Second time, ran nicely and uploaded to chipkit. And I did use a 512b thus time.