[Mspgcc-users] MSPDebug version 0.11
A new version of MSPDebug is available now. There are still a few outstanding issues with some chips, but there's been quite a lot added so I thought it was about time to put together a new release. Notable features in this one: * Support for programming and debugging 20-bit devices. * Support for MSP430X instruction set. * Support for new chips: MSP430F2234, CC430F5137, MSP430F2618, MSP430F1612, MSP430F47197, MSP430F1232, MSP430F413, MSP430F2370. * Bug fixes: RF2500 support on OS/X, chip identification using FET. * Added quiet mode to supress debug output. * Faster gdb transfers. * Faster polling with FET driver (quicker single-stepping and breakpoint detection). * Commands can now be issued, and output received, via the gdb interface (using monitor). * Support for FET430UIF firmware updates via BSL. Available, as always, from: http://mspdebug.sourceforge.net/download.html - Daniel
Re: [Mspgcc-users] MSPDebug version 0.11
Hi Daniel, I don't know what you changed, but it now also works with my FET firmware version. Awesome! This should save me lots of time compared to using Windows msp430-jtag through Wine. Thanks! Oh, I did notice a warning when programming a HEX file, on the next-to-last line: $ mspdebug uif -j -d /dev/ttyUSB0 prog build/lnode_custom/main.ihex Trying to open UIF on /dev/ttyUSB0... Initializing FET... FET protocol version is 20401004 Configured for JTAG (2) Sending initial reset... Set Vcc: 3000 mV Device ID: 0xf249 Device: MSP430F249 Code memory starts at 0x1100 Number of breakpoints: 3 Erasing... Programming... Writing 128 bytes to 8000... Writing 128 bytes to 8080... [snip] Writing 128 bytes to 8a00... Writing 128 bytes to 8a80... Writing 22 bytes to 8b00... warning: ihex: unknown record type: 0x03 Writing 32 bytes to ffe0... I'll attach the HEX file, it's a simple flash a LED test program. It seems to be working just fine, though. Michiel -Original Message- From: Daniel Beer [mailto:dlb...@gmail.com] Sent: donderdag 9 september 2010 5:52 To: GCC for MSP430 - http://mspgcc.sf.net Subject: [Mspgcc-users] MSPDebug version 0.11 A new version of MSPDebug is available now. There are still a few outstanding issues with some chips, but there's been quite a lot added so I thought it was about time to put together a new release. Notable features in this one: * Support for programming and debugging 20-bit devices. * Support for MSP430X instruction set. * Support for new chips: MSP430F2234, CC430F5137, MSP430F2618, MSP430F1612, MSP430F47197, MSP430F1232, MSP430F413, MSP430F2370. * Bug fixes: RF2500 support on OS/X, chip identification using FET. * Added quiet mode to supress debug output. * Faster gdb transfers. * Faster polling with FET driver (quicker single-stepping and breakpoint detection). * Commands can now be issued, and output received, via the gdb interface (using monitor). * Support for FET430UIF firmware updates via BSL. Available, as always, from: http://mspdebug.sourceforge.net/download.html - Daniel
Re: [Mspgcc-users] MSPDebug version 0.11
Hi Daniel, Would it be possible to add mass erase and info erase commands in a future version? Kind regards, Michiel -Original Message- From: Daniel Beer [mailto:dlb...@gmail.com] Sent: donderdag 9 september 2010 5:52 To: GCC for MSP430 - http://mspgcc.sf.net Subject: [Mspgcc-users] MSPDebug version 0.11 A new version of MSPDebug is available now. There are still a few outstanding issues with some chips, but there's been quite a lot added so I thought it was about time to put together a new release. Notable features in this one: * Support for programming and debugging 20-bit devices. * Support for MSP430X instruction set. * Support for new chips: MSP430F2234, CC430F5137, MSP430F2618, MSP430F1612, MSP430F47197, MSP430F1232, MSP430F413, MSP430F2370. * Bug fixes: RF2500 support on OS/X, chip identification using FET. * Added quiet mode to supress debug output. * Faster gdb transfers. * Faster polling with FET driver (quicker single-stepping and breakpoint detection). * Commands can now be issued, and output received, via the gdb interface (using monitor). * Support for FET430UIF firmware updates via BSL. Available, as always, from: http://mspdebug.sourceforge.net/download.html - Daniel
[Mspgcc-users] latest mspgcc vs latest webpage/wiki/etc...
What's the status of the new git-based mspgcc4 (with TI includes/ etc)? Sourceforge and/or the wiki still don't mention it at all, and I can't get it to install libc due to fairly obvious problems that ought to be cross-platform... Thanks Bill W
Re: [Mspgcc-users] latest mspgcc vs latest webpage/wiki/etc...
I'm doing the work in local git repositories that are mirrors of the official GNU binutils and gcc ones. I'd been reluctant to push them to sourceforge because of size, but in the end I think that's the right solution. The status is that I've successfully built applications with hand-crafted linker scripts, and all chip-specific (as opposed to feature-driven) data has been eliminated from binutils and gcc. It's not really ready for anybody else to use; I need some updates from TI, and a way to package the MSP430 binutils scripts, then I can document what I did and why and push things to a repository where people can play. The initial releases will *not* have build script support: you'll need to be able to build and install binutils and gcc and msp430-libc manually. Unfortunately, though People Power is committed to community support and has approved my work on this, there are some short-term deadlines that are impacting how much time I can spend on it this month. I'm fighting to restore mspgcc's priority. Nonetheless, if you can't get ti-20100815 to build with the current mspgcc4 on any reasonable platform, that's something we need to get fixed ASAP. Can you provide more details, here or as a ticket on the mspgcc project (or is there already a ticket I've missed)? Peter On Thu, Sep 9, 2010 at 4:27 AM, William Chops Westfield wes...@mac.comwrote: What's the status of the new git-based mspgcc4 (with TI includes/ etc)? Sourceforge and/or the wiki still don't mention it at all, and I can't get it to install libc due to fairly obvious problems that ought to be cross-platform... Thanks Bill W -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] Patch for msp430-libc
This patch fixes a minor typo in the msp430x54xx.h file.
Re: [Mspgcc-users] latest mspgcc vs latest webpage/wiki/etc...
On Sep 9, 2010, at 5:36 AM, Peter Bigot wrote: Nonetheless, if you can't get ti-20100815 to build with the current mspgcc4 on any reasonable platform, that's something we need to get fixed ASAP. Can you provide more details, here or as a ticket on the mspgcc project (or is there already a ticket I've missed)? I have problems with building libc, as I mentioned. MacOS 10.5.8 I have: Select GCC version to build: 1) gcc-4.4.4 2) gcc-4.4.3 3) none Enter your choice (1-3) [1]: 1 Select GDB version to build: 1) gdb-7.1 2) gdb-7.0.1 3) none Enter your choice (1-3) [1]: 1 Select Insight version to build: 1) insight-6.8-1 2) none Enter your choice (1-2) [1]: 2 Select libc version to build: 1) 20100815 2) ti_20100829 3) ti_20100815 Enter your choice (1-3) [1]: 2 Strip debug information from executables after install? (y/n) [y] Enter target toolchain path [/opt/msp430-gcc-4.4.4]: /sw/cross/msp430-ti And it eventually fails: msp430-gcc -x assembler-with-cpp -c -mmcu=msp3 -I./../include/ti - I./../include -I. ./stdlib/div.S -o Build/msp3/div.o ./stdlib/div.S: Assembler messages: ./stdlib/div.S:9: Error: unknown opcode `xpushm' ./stdlib/div.S:24: Error: unknown opcode `xpopm' make[1]: *** [Build/msp3/div.o] Error 1 Looking at div.S, there is: #include../core_common.inc /* ldiv() is the same as __divmodsi4() in libgcc */ .section .text .global div div: ;; save clobbers first #if defined(__MSP430X__) XPUSHM #2, r11 #else But elsewhere (in core_common.inc), code under __MPS430X__ is completely disabled and so XPUSHM does not get defined. I don't see how this compiles on any platform... /* pab 20100724 Disable MSP430X recognition: the required supporting * infrastructure has not been integrated into mpsgcc4. */ #if 0 /* defined(__MSP430X__) */ #if defined(__MSP430X_ADDR_16BIT__) #define XBR br #define XCALL call #define XRETret #define XMOVA mov #define XCMPcmp #else #define XBR bra #define XCALL calla #define XRETreta #define XMOVA mova #define XCMPcmpa #endif #if defined(__MSP430X_REGS_16BIT__) #define XPUSH pushx.w #define XPOPpopx.w #define XPUSHM pushm.w #define XPOPM popm.w #define XMOVmovx.w .equPUSH_BYTES, 2 #else #define XPUSH pushx.a #define XPOPpopx.a #define XPUSHM pushm.a #define XPOPM popm.a #define XMOVmovx.a .equPUSH_BYTES, 4 #endif #else #define XBR br #define XCALL call #define XRETret #define XMOVmov #define XCMPcmp #define XPUSH push #define XPOPpop #define XMOVA mov .equPUSH_BYTES, 2 #endif
Re: [Mspgcc-users] latest mspgcc vs latest webpage/wiki/etc...
completely disabled and so XPUSHM does not get defined. I don't see how this compiles on any platform... Neither do I. It only affects the msp3 and msp5 multilibs, which I don't use since until last week I didn't have relevant hardware, and the Makefile (under Linux) just blows right over the error for those two sub-builds. SF ticket 3062827 on mspgcc created, fix submitted and merged to next. Patch attached. Please let me know whether it fixes the problem. I'll try to do better at scanning the make output. Peter
Re: [Mspgcc-users] MSPDebug version 0.11
I would ask that erase main and erase info be supported as they are for msp430-gdbproxy instead of creating new commands. Jesse On Thu, Sep 9, 2010 at 1:17 AM, Michiel Konstapel m.konsta...@sownet.nl wrote: Hi Daniel, Would it be possible to add mass erase and info erase commands in a future version? Kind regards, Michiel -Original Message- From: Daniel Beer [mailto:dlb...@gmail.com] Sent: donderdag 9 september 2010 5:52 To: GCC for MSP430 - http://mspgcc.sf.net Subject: [Mspgcc-users] MSPDebug version 0.11 A new version of MSPDebug is available now. There are still a few outstanding issues with some chips, but there's been quite a lot added so I thought it was about time to put together a new release. Notable features in this one: * Support for programming and debugging 20-bit devices. * Support for MSP430X instruction set. * Support for new chips: MSP430F2234, CC430F5137, MSP430F2618, MSP430F1612, MSP430F47197, MSP430F1232, MSP430F413, MSP430F2370. * Bug fixes: RF2500 support on OS/X, chip identification using FET. * Added quiet mode to supress debug output. * Faster gdb transfers. * Faster polling with FET driver (quicker single-stepping and breakpoint detection). * Commands can now be issued, and output received, via the gdb interface (using monitor). * Support for FET430UIF firmware updates via BSL. Available, as always, from: http://mspdebug.sourceforge.net/download.html - Daniel -- This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSPDebug version 0.11
On Thu, Sep 09, 2010 at 10:40:11AM +0200, Michiel Konstapel wrote: Hi Daniel, I don't know what you changed, but it now also works with my FET firmware version. Awesome! This should save me lots of time compared to using Windows msp430-jtag through Wine. Thanks! Oh, I did notice a warning when programming a HEX file, on the next-to-last line: $ mspdebug uif -j -d /dev/ttyUSB0 prog build/lnode_custom/main.ihex Trying to open UIF on /dev/ttyUSB0... Initializing FET... FET protocol version is 20401004 Configured for JTAG (2) Sending initial reset... Set Vcc: 3000 mV Device ID: 0xf249 Device: MSP430F249 Code memory starts at 0x1100 Number of breakpoints: 3 Erasing... Programming... Writing 128 bytes to 8000... Writing 128 bytes to 8080... [snip] Writing 128 bytes to 8a00... Writing 128 bytes to 8a80... Writing 22 bytes to 8b00... warning: ihex: unknown record type: 0x03 Writing 32 bytes to ffe0... I'll attach the HEX file, it's a simple flash a LED test program. It seems to be working just fine, though. That's good news. The warning is nothing to worry about. I should probably remove it actually. Record type 03 specifies the initial PC value, which is unneccessary for the MSP430. - Daniel
Re: [Mspgcc-users] MSPDebug version 0.11
On Thu, Sep 09, 2010 at 11:17:50AM +0200, Michiel Konstapel wrote: Would it be possible to add mass erase and info erase commands in a future version? This has been on my TODO list for a while, and it would be a good thing to add. I was thinking something like an extra parameter to the erase command (e.g. erase mass, erase info). - Daniel
Re: [Mspgcc-users] MSPDebug version 0.11
On Thu, Sep 09, 2010 at 09:54:58AM -0800, Jesse Frey wrote: I would ask that erase main and erase info be supported as they are for msp430-gdbproxy instead of creating new commands. Well, there we go... I guess I should've looked at the other replies before I sent mine :). - Daniel
