Thanks for the comments. The problem with the 4618 definitely appears to be SVS related - I held SVSIN/P6.7 high when the device was powered up, which immediately made it visible via the JTAG. I then dumped some 4618 compiled code in, and it now appears back to normal.
I still have the inaccessible problem with the 2013 on the board. This does not have an SVS module, so its not quite the same problem, but sounds something similar... I'm away for a few days, so I'll have a good look when I return. Any other ideas welcome. Andrew -----Original Message----- From: JMGross [mailto:msp...@grossibaer.de] Sent: Thursday, 27 May 2010 4:40 a.m. To: MSPGCC mailing list, Subject: Re: [Mspgcc-users] Cannot access TI MSP Experimenters board Hi Carl, I didn't mean this thread (I joined the forum in March this year, so it was well before my time) but another one. There it was a jumper thing. But good to know you case too. I wonder why the SVS register in the 4618 isn't reset by a power-down. On all MSPs I worked with so far, the SVS (If any) setting survives a reset but not a POR. But maybe it only works if you power the MSP from the FET and switch power on after RESET is already held low, so the user code won't start and alter the SVS before the JTAG programming sequence can kick in. I think this should be possible with the Elprotronic software which will enable/disable power on the USB FET automatically, depending on your setting. I also noticed that you can erase the flash by applying a high voltage or high temperature. Some of the PICs we used lost their programming during soldering (the MSPs are programmed later, so we never noticed this) and I think we hat an MSP losing the flash content when it got accidentally stuffed with 5V. (as well as some pics with >7V when the 4V regulator failed). It's not a recommended procedure anyway. JMGross ----- Ursprüngliche Nachricht ----- Von: Carl An: GCC for MSP430 - http://mspgcc.sf.net Gesendet am: 25 Mai 2010 18:16:54 Betreff: Re: [Mspgcc-users] Cannot access TI MSP Experimenters board I had a FG4618 experimenters board that I accidentally programmed with F2618 code. This caused the board to be no longer accessible via JTAG. For the solution see: http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_ mcus/f/166/p/18632/71831.aspx#71831 Carl On Mon, 2010-05-24 at 17:51 +1200, Andrew McLaren wrote: > I'm using the mspgcc toolchain with a TI USB FET. I've been struggling > to get the toolchain to communicate with a TI MSP-EXP430FG4618 > experimenters board (this is the board with both a 4608 and 2013 > processors). The scenario I have is as follows; > > If I try and attach to either of the processors via their respective > JTAG connectors using msp430-gdbproxy, MSP430_Identify advises that > either it can't access the device, or the device is not supported. > > The same toolchain will happily connect to a 2131 or 439 I've tried it > with (both on simpler header boards). > > The msp430 and hil dll's have been updated to the latest available > from TI. However, I doubt that there is any problem with the specific > device variants, as neither of these is that new. > > Switching the TI FET to an Olimex JTAG interface gives the same > results (still with the mspgcc toolchain). > > I've reinstalled the original IAR software, but this doesn't want to > talk to the board either. Similarly with Olimex's software talking > through the Olimex JTAG. > > This would all seem to imply that the problem is with the experimeters > board itself rather than the toolchain, but this also doesn't gell. > This JTAG interfaces to this board were working about 6 weeks ago. > Other priorities, so it was parked, but now the RS232 interface on > this board would be quite useful. Since then, nothing has been touched > with the Experimenters board, but I've done a lot of playing with the > various toolchains as part of getting the Olimex JTAG working. The > 2013 is definitely running (its got some code loaded that blinks a led > ocassionally). Even if I had somehow managed to damage something, it > seems highly unlikely that it would affect both processors on the > board the same. I'm suspicious that there is something related to the > JTAG interfaces on this board, but that's a real guess. > > I have considered the possibility that I've blown the JTAG fuses, but > again, I'd imagine that it would be hard to do this accidentally, and > to both chips? Its not something I've played with at all. How does a > chip with a blown fuse appear externally? > > Any other ideas or things I could look at? > > Regards > > Andrew > > > ---------------------------------------------------------------------- > -------- > > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------ ------ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
