Re: [Mspgcc-users] Problems programming MSP430F2252

2012-09-16 Thread Daniel Beer
On Fri, Sep 14, 2012 at 07:20:27PM -0500, Peter Bigot wrote: > I can confirm that with FET firmware 2.04.09.001 and the current head > of mspdebug git, it is necessary to specify -d /dev/ttyUSBwhatever, > where with 2.04.05.003 mspdebug figured things out itself without > having to be told the spec

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-09-14 Thread Peter Bigot
I can confirm that with FET firmware 2.04.09.001 and the current head of mspdebug git, it is necessary to specify -d /dev/ttyUSBwhatever, where with 2.04.05.003 mspdebug figured things out itself without having to be told the specific device to use. Odd. I find that annoying and will stick with 2

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-23 Thread Robert Henig
Hi Daniel, The FET_UIF works with 0.20 but only if I specify -d /dev/ttyUSB0. Both the rf2500 and uif correctly identify the MSP430F2252. Thanks for your help. Bob. On Aug 22, 2012, at 7:39 PM, Daniel Beer wrote: > On Wed, Aug 22, 2012 at 04:51:07PM -0700, Robert Henig wrote: >> On Aug 22,

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-23 Thread Robert Henig
Hi Daniel, Looks like it was added in 0.20. That version works. I'll let you know if that also helps with the FET-UIF later today. Thanks, Bob. On Aug 22, 2012, at 9:46 PM, Daniel Beer wrote: > On Wed, Aug 22, 2012 at 09:36:36PM -0700, Robert Henig wrote: >> I tried that and it failed with

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Daniel Beer
On Wed, Aug 22, 2012 at 09:36:36PM -0700, Robert Henig wrote: > I tried that and it failed with errors. Output is at the end of the previous > email. I tried forcing MSP430G2553 and erase worked. Go figure? Oops, I missed that part. Just checking the git log, support for the F2252 was added in

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Daniel Beer
On Wed, Aug 22, 2012 at 04:51:07PM -0700, Robert Henig wrote: > On Aug 22, 2012, at 4:10 PM, Daniel Beer wrote: > > > As for your FET-UIF, do you know what firmware version you have > > installed on it? If it's V3, you'll need to use the tilib driver. > > The FET is version 2.04.09.001. Ok, then

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Daniel Beer
On Wed, Aug 22, 2012 at 04:36:23PM -0700, Robert Henig wrote: > I'm using version 0.18 of mspdebug. I start it using the command 'mspdebug > rf2500'. I am seeing something unusual with the startup output. The device > I'm using is the F2252 but it's getting identified as F2272. It also is >

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Robert Henig
On Aug 22, 2012, at 4:10 PM, Daniel Beer wrote: > As for your FET-UIF, do you know what firmware version you have > installed on it? If it's V3, you'll need to use the tilib driver. The FET is version 2.04.09.001. I've tried these two commands with similar results: $ sudo mspdebug uif MSPDebug

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Robert Henig
I'm using version 0.18 of mspdebug. I start it using the command 'mspdebug rf2500'. I am seeing something unusual with the startup output. The device I'm using is the F2252 but it's getting identified as F2272. It also is showing the code start at 0x8000 instead of 0xc000. Here is the outpu

Re: [Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Daniel Beer
On Wed, Aug 22, 2012 at 11:36:10AM -0700, Robert Henig wrote: > I have a custom board with a F2252 that is programmable using a FET-UIF from > a windows system using IAR and FETPro-Lite. On Ubuntu 12.04 I am unable to > get the FET-UIF to work with mspdebug ( I did see the thread about this > p

[Mspgcc-users] Problems programming MSP430F2252

2012-08-22 Thread Robert Henig
I have a custom board with a F2252 that is programmable using a FET-UIF from a windows system using IAR and FETPro-Lite. On Ubuntu 12.04 I am unable to get the FET-UIF to work with mspdebug ( I did see the thread about this problem with OS X and non of that helped ). By hijacking the pins from