On Wed, Sep 22, 2010 at 07:00:09PM -0500, Peter Bigot wrote:
> No go.  Previous attempt was with:
> 
> FET protocol version is 20404000
> 
> Just downloaded the latest Code Composer Studio and updated the FET firmware
> now to:
> 
> FET protocol version is 20405003
> 
> Same behavior.  FWIW, I've never seen a FET version 20305000; where did you
> get it?
> 
> If it matters, I do know the EXP430F5438 has a 5438 on it, not a 5438A.  Now
> that I've dug up an old PC with a Windows XP license I was able to snare
> some sniffusb output which I've forwarded to Daniel in hopes he can help.
> 
> Once either that problem is fixed, or support for the FG4618 is added
> (another board I have), I'll at least have hardware that supports more than
> 64KB of memory.  Doesn't fix the time availability issue, unfortunately.

Hi Peter,

Sorry for the late reply -- I've been out of town the past week.

Anyway, I'll take a look at the sniffusb output you've sent and see
what I can put together. I have an FG4618 which was working as at
version 0.8, but I've just tried it again and apparently I've broken
something.

However, I did manage to get it working with:

    dlb...@euler:~$ ./mspdebug --no-reset -jd /dev/ttyUSB0 uif
    Trying to open UIF on /dev/ttyUSB0...
    Initializing FET...
    FET protocol version is 20107000
    Configured for JTAG (2)
    Set Vcc: 3000 mV
    Device: MSP430FG461x
    Code memory starts at 0x3100
    Number of breakpoints: 8

Perhaps I need to do something about the default start-up behaviour.
The initial reset is required in some cases, but creates problems in
other cases.

Cheers,
Daniel

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to