chipKIT® Development Platform

Inspired by Arduino™


Created Sat, 06 Sep 2014 20:28:19 +0000 by W9BEL


Sat, 06 Sep 2014 20:28:19 +0000

The IOShield EEProm library don't appear to work with the latest MPIDE 0821. The included example won't run either. Compile and upload with no errors but no results in the serial window.

Everything works fine the MPIDE 0316.

I have several sketches that use 256 EEProms and all work fine with 0316 and none work with 0821.

On the sketches with a LCD I get nothing. Appears to be a dead UNO32. Compile and upload with 0316 and all is well again.

Am I missing something??


Bill Bell


Wed, 17 Sep 2014 19:53:19 +0000


MPIDE 0821 has a new compiler that does not play well with the IOEEPROM library. The current solution is to use 0316 version.


Jesse N


Thu, 18 Sep 2014 17:41:00 +0000

Thanks for the reply.

I figured it must be the compiler. I have a couple of libraries that work with the 0316 version and neither 1 with work with 0821.

Bill Bell


Tue, 23 Sep 2014 20:58:19 +0000

Hi Bill,

Can you help us isolate this problem? Is there anything in common regarding the libraries that don't work with 0821? Or, can you trim it down to a short example of the problem?



Wed, 24 Sep 2014 17:12:45 +0000

The easiest example is the EEPROM example that is included with the Basic IO Shield download from the Digilent web site. The library and example is available at,892,936&Prod=CHIPKIT-BASIC-IO-SHIELD

I am not using their board but a proto shield with a 256k eeprom installed. Works fine with the 0316 MPIDE version but don't work with any version after that including the test versions. I didn't check all test versions but quite a few of them.

Compile and upload ok with no errors. The UNO32 appears to be dead. I have the example with a I2C LCD display included and I never get anything printed on the display. Comment out the EEPROM items and the display works fine.

Whatever sketch I use works fine if compiled and uploaded with the 0316 version.

Bill Bell


Mon, 29 Sep 2014 20:44:08 +0000

Thanks. I believe that we have isolated the issue. We are tracking it here: