To get the Winzip password - please: E-mail for the password - instructions are on my site. Note the http link for this file is currently broken.
Known Issues with the Port:
*) Timer for LCD PWM needs to be fixed.
Misc:
To see the port run above 0xFFFF - you need to modify the linker command file - the command file in called out in the project - but it is not included with the files. Modify the code section appropriately to see code above the 64K Boundary running in the debugger.
For some reason, the Timer issue with the backlight control isn’t such an issue if you are running with USB power and running the debugger - if you run with battery power, it is more pronounced. I will fix this issue shortly, or as an exercise, please feel free to move the LCD PWM Backlight timer to one of the many available timers.
Another important item here -
If you wholly relocated the UserExperience code to be >0x10000 - as is ‘easy’ in IAR and a bit more of a chore in CCE - so I would think this goes more for those working with IAR - the Voice Rec demo will erase that part of memory that will lock the MSP430F541x/543x parts - so be warned. If you are using the MSP-EXP430F5438 - then that board doesn’t directly support BSL without rework so you will be in a bind if you don’t have extra parts on hand. So as another exercise - the Voice Rec code at least - in particular the piece that erases before it records - needs to be modified so that it is (functionally) relocatable.
Due to some interesting discussions with some of you - I have made the Context Save and Restore routines *slightly* more efficient - over time this adds up however. And also have updated port.c. Note, this make the 430X Port somewhat incompatible with the previous (non-MSP430X) ports - *unless* - you want to ‘fix’ that up - meaning - there is a way to make the two more compatible…
Anyway - I have updated the port to the lastest IAR toolset plus the core files are updated to 5.4.2. If you want the port to behave identically to the original TI code - then make sure all of the LPM statements are uncommented - I think this means chiefly the first one in UserExperience.c -
*ALSO* - As mentioned above - the Audio Record demo. is not debugged. TI makes use of numerous addresses >0x10000 that the demo. uses - so if you run that - and your code is >0x10000, you will wipe out your code and possibly lock the part. I haven’t had time to fully debug the audio code - but it should work as long as it is relocated and bounds checked.
I have updated the demo again - added a proper HW init routine that should address some of the comments I have received about the demo. having ‘flakey’ behavior. Note this isn’t the case with the CCE demo since it does not currently include the ‘UserExperience’ code but I am adding that under CCS v4 - *and* I will *fix* the audio.c code soon so that it works OK with the port.
Please visit the web-site to pick up the latest - I will post a message when the new CCS v4 port is done.
The audio record demo is *fixed* and I have updated the IAR port. I will post the CCE port soon. Here’s the updated link:
I haven’t exhaustively debugged the audio code - so don’t be surprised if you experience a glitch or two.
Note the audio demo code uses memory that is >0x10000 - so, if you want to put code in that section, be warned the audio demo. uses it - and will erase your code and could possibly lock the part.