On 2007-12-14, Grant Edwards <[email protected]> wrote:
>>> Has anybody worked with the MSP430F2410 yet?
>>
>> If you are using Windows its OK.
>
> Is that true for 2330 as well?
Apparently not for any value of "using Windows" that I can come
up with.
I installed IAR kickstart and verified that its debugger can
talk to the 2330 (I can download and run the LED flashing demo
program). When I run msp430-gdbproxy using the msp430.dll and
hil.dll files from the IAR install I still get this:
notice: msp430: TI USB FET self-test requested
debug: MSP430_Initialize()
debug: MSP430_FET_SelfTest()
notice: msp430: Self test passed
debug: MSP430_Initialize()
debug: MSP430_Configure()
debug: MSP430_VCC(3000)
debug: MSP430_Identify()
error: msp430: Could not find device (or device not supported) (4)
debug: MSP430_VCC(0)
debug: MSP430_VCC(3000)
debug: MSP430_Reset(ALL_RESETS)
debug: MSP430_Close()
Assertion failed: !msp430_status.is_open, file target_msp430.c, line 745
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Since the DLL files appear to work with the IAR debugger is it
safe to assume that they're up-to-date enough?and that it's
msp430-gdbproxy itself that needs to be udpated?
What does it take to add a new device type to msp430-gdbproxy?
Is there anything I can do to help?
--
Grant Edwards grante Yow! I smell a RANCID
at CORN DOG!
visi.com
