Most of the this week was spent studying the schematic and design files (from Hong’s computer) and comparing the MCU on the current Moo design (Part # MSP430F2618) with the Wolverine MCU (Part # MSP430FR5969). Essentially, I have been mapping out the necessary steps that will be needed to make the migration from the current MCU to the Wolverine chip.
More info on Wolverine chip available here.
I spent time studying the schematic design and board layout for several different iterations of the Moo devices (Moo 1.0, Moo 1.1, Moo 1.2, Moo 1.3). Primarily I was interested in seeing what past work had been done in regards to the board design and how it has progressed through each iteration. See embedded document below for a brief overview of some of the differences that I noticed.
After looking over the features of each of the different board revisions, I plan to branch off of the design labeled Moo 1.1_03102011. This design represents the current version of the Moo devices so we know that it is a working design. The later designs seemed to have been created to test other aspects of the devices, such as…
- comparison of linear voltage regulator with switching regulator, toggle-enabled
- new MCU chip, Part # CC430F6137
I copied the appropriate design files from Hong’s computer and plan on working in the Altium Designer 10 environment that is installed on the CAEN computers (virtual connection).
Notes/Questions on Wolverine Migration
- The Wolverine chip uses a 48-pin QFN package as opposed to a 64-pin LQFP
—> may need to completely reroute this portion of the PCB board, depending on pin placement and extent of similarity with F2618 chip.
- Ordered and received 2 Samples of the (prototype) Wolverine Chip. Is there a place that we can go to fabricate (and assemble) 2 boards only? SierraExpress? Should I place another order for Samples (max. 2 chips at a time)?
Next Steps for Migration:
- make integrated component for 48-pin QFN package with schematic symbol in Altium 10
- place and route component onto the board. Study datasheet for details on pin descriptions.
Moo Concrete Deployment Project
Objective: Embed several of our current Moo devices into concrete for real-world testing.
Task: find out which firmware was used in previous concrete deployment. Need to enable a Kill switch, and possibly OTA updates.
From Ben, current version of firmware found here.
Note: Firmware does have a kill switch, but does not have support for over-the-air updates.
- validate Moo devices with current firmware.
- possibly modify FW to support OTA updates??