Re: [Mspgcc-users] MSPDebug version 0.9

[<da...@to...>]

Andres Vahter writes:
> Is it possible to program msp430f2234 MCU with EZ430-RF2500 board
> and mspdebug.  EZ430-RF2500 board comes with msp430f2274 MCU and it
> differs from f2234 only from RAM size as far as I know.
> 
> I made a led togglerer for f2234, i can upload it, but it doesn't
> toggle pin.
> 
> #include    "msp430x22x4.h"
> volatile unsigned int i;
> 
> int main(void) {
>     WDTCTL = WDTPW + WDTHOLD;
>   
>     P2DIR |= 0x01;
>     
>     for(;;)
>     {
>         P2OUT ^= 0x01;
>         i = 50000;
>         while (i != 0) { i--; }
>     }  
> }
> for( ; ; )
> 
> 
> Daniel, could you confirm that msp430f2234 is supported by mspdebug.

I sent a reply to Andres earlier, but only just realised that I didn't
copy the list.

The gist of it was that the 2234 isn't explicitly supported, but you
might be able to make it work by applying the following patch and then
using:

    mspdebug --fet-force-id msp430f2274 ...

This patch just alters the RAM size for the MSP430F2274, nothing else.

diff --git a/fet_db.c b/fet_db.c
index 1b412fd..5f9e3b5 100644
--- a/fet_db.c
+++ b/fet_db.c
@@ -370,7 +370,7 @@ static const struct fet_db_record fet_db[] = {
                .msg29_params = {0x00, 0x39, 0x31},
                .msg29_data = {
                        0x00, 0x80, 0xff, 0xff, 0x00, 0x00, 0x00, 0x10,
-                       0xff, 0x10, 0x40, 0x00, 0x00, 0x02, 0xff, 0x05,
+                       0xff, 0x10, 0x40, 0x00, 0x00, 0x02, 0xff, 0x03,
                        0x00, 0x00, 0x00, 0x00, 0x02, 0x00, 0x01, 0x00,
                        0x01, 0x00, 0xd7, 0x60, 0x00, 0x00, 0x00, 0x00,
                        0x08, 0x07, 0x10, 0x0e, 0xc4, 0x09, 0x70, 0x17,