This update requires a Netduino Go running v4.2.0.1+ firmware.
In April, we launched the Shield Base to introduce GoBus Virtual I/O. With the release of the GoBus 1.5 specification, we've updated the Shield Base to GoBus 1.5.
This firmware uses the GoBus 1.5 UART transport, so it temporarily requires use of 4 GoPorts (1-4 or 5-8). We will remove this restriction later this season by moving to the fast GoBus 1.5 SPI transport.
This firmware includes the following updates:
1. GoBus 1.5 transport: error-correction with CRCs, frame acknowledgements, retries, etc.
2. InterruptPort support (pins D2-D13, although A0-A5 can be used by advanced users)
3. New ShieldBase.PWMChannels and ShieldBase.AnalogInputs enumerations (matching Netduino 4.2)
This firmware also includes the previous updates:
1. PWM no longer stops working 'randomly'
2. PWM scale now works properly
Known issues:
1. Pins D0/D1 are occupied by the NETMF debug channel. We'll free these up in an upcoming update.
NOTE: if you are using your Shield Base (with upgraded STM32F2 chip) as a standalone NETMF board, you'll want to continue using the production 4.2.0.0 NETMF firmware.
To upgrade your Shield Base:
1. Plug your Shield Base into GoPort 5 of your Netduino Go.
2. Deploy the attached updater app, and watch your Output window.
3. When prompted, press the Netduino Go's onboard button to start the flashing process.
4. While flashing your Shield Base, socket 5's LED will flash and the Output window will provide status.
5. When the Shield Base is completely updated, the white power LED will flash.
After the upgrade, simply deploy a new app to your Netduino Go mainboard. If you have trouble communicating with the shield base, power cycle your Netduino Go.
Please post in this thread if you have any troubles.
Thank you for beta testing the Shield Base,
Chris
P.S. We've discovered a quirk in the NETMF STM32 flash drivers which seems to intermittently affect deployment of really large apps like this one. If you run into troubles deploying this app (or another app immediately after this one), you can re-flash your mainboard. We're looking into it, and hope to contribute back any bug fixes to the NETMF core.