Matthias, I do not have write access to the WIKI. So I guess either of us need to get appropriate permissions from the moderator.
I do have a sourceforge account with the username 'msjaved' and be happy to put up the page on wiki if the moderator can put me in the editors list. SJ _____ From: Matthias Hartmann [mailto:[email protected]] Sent: 27 February 2009 15:44 To: GCC for MSP430 - http://mspgcc.sf.net Subject: Re: [Mspgcc-users] Connection failure during close and re-openmsp430-gdbproxy by msp430-insight Shoaib, I realy appreciate that the tutorial becomes a part of the Wiki (http://apps.sourceforge.net/mediawiki/mspgcc/index.php?title=MSPGCC_Wiki). What do I need to edit the Wiki and upload files? An SourceForge Account with specific rights? ...? Or will you put it on the WIKI page? Matthias 2009/2/27 Shoaib Javed <[email protected]> Matthias, Nice put together tutorial. Can it be part of the MSPGCC's wiki? Thanks, SJ -----Original Message----- From: Matthias Hartmann [mailto:[email protected]] Sent: 26 February 2009 18:23 To: GCC for MSP430 - http://mspgcc.sf.net <http://mspgcc.sf.net/> Subject: Re: [Mspgcc-users] Connection failure during close and re-open msp430-gdbproxy by msp430-insight Tim, not a solution of the actual problem, but may be a solution for getting a GUI in front of gdb. Try Eclipse - I am using Eclipse, mspgcc, mspgdb and the MSP-FET430UIF with good success. Tutorial: http://matthias-hartmann.blogspot.com/ Matthias Drmn4ea schrieb: > Matthias, > Thanks for the reply. I tried this, but no change in behavior (the debugger > seems to work equally well - or not - with --spy-bi-wire parameter). I have > been intermittently successful getting Insight to the point of stepping > through an .elf and actually debugging, provided it never disconnects and > reconnects to gdbproxy in the process. Smelling a possible hardware issue I > tried a couple hail-marys (e.g. varying the capacitance on RST\ between 0 > and the 2.2nF max suggested by the datasheet), and a bit on the SBW data > line, but no improvement in behavior. Scoping these and the Vcc rail suggest > they are relatively clean. > > Purely guessing, but it feels like a possibility that Insight is simply > trying to reconnect too fast, and the chip (via gdbproxy's required > housekeeping between dis- and reconnect) can't keep up. Are there any gdb > options (or gdb-insight, etc.) to slow it down? > > Should I just bite it and embrace command-line gdb proper? > > Tim > > > Matthias Hartmann-2 wrote: > >> I am not using spy-bi-wire, but form reading the output of >> msp430-gdbproxy.exe --help msp430 >> I would guess, you should add parameter --spy-bi-wire to the call to >> msp430-gdbproxy.exe. >> >> msp430-gdbproxy.exe --debug --port=2000 msp430 --spy-bi-wire USBFET >> >> > > ---------------------------------------------------------------------------- -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users ---------------------------------------------------------------------------- -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
