> > This is because the 54xx are devices with X architecture and there are > > some changes in JTAG for thouse MCU's. JTAG version is changed too, > > that's one of reasons (but not the only one) why gdbproxy is broken for > > the 54XX. JTAG Memory writing routines are changed also. > > Does this mean that I cannot even use MSP430-jtag to program these processor > (with or without use of the additional FLASH segments)?
It doesn't work for me. It even can't initialize a device, I think it's because the JTAG ID has changed. But this is not the only change - JTAG initialization sequence is unclear, we've used logical analyzer to sniff how IAR works. Seems that memory writing sequences are changed too. > I never used a debugger on MSPs, as it is of no use when you have to work on > realtime communication with other devices. You usually can't control them all > simultaneously, so as soon as you hit a > breakpoint, everything is out-of-sync and all you can do is to take a moments > snapshot and start over from zero again. Yeah, but sometimes a debugger is quite useful. Anyway, I not plan to implement it right now, cause I'm totally out of schedule due to problems with 5418 programming. --- Dmitry > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
