This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
We are currently preparing the final v1.00 release of Grace, which we expect to be posted at the end of this month. Because the opportunity for further changes to this version of the product is rapidly closing, we would like to encourage everyone to post your feedback, including questions, issues and comments, to this forum.
Thanks!
MSP430 Programming Team
Hi Russel,
first of all: Grace is great!
Well, besides using Grace to generate peripheral initialization code it would be good include a peripheral driver library (in source code --> don't forget the IAR users which were waiting for a stand alone release of Grace) for dealing with the peripherals.
I.e.:
1) I2C
There are a lot of questions related to I2C on the E2E forums. So, why not include sources for sending/receiving data (multiple bytes!) via I2C? Maybe you can generate a new tab (window) in Grace were the user can select if he wants to use the routines, how large the TX/RX buffer is etc.
2) UART
The new value line devices will have a hardware UART --> give the users the routines for dealing with it at a 'click'
3) Use of INFO memory for storing data
Many questions on this topic too. So, since Grace configures the Flash memory controller, why not include a piece of code for using it?
...
Rgds
aBUGSworstnightmare
Adding support for other MSP430 devices such as MSP430F5438 (and related) would be great.
**Attention** This is a public forum