http://blog.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10564 <pre>Dear All, I am porting some old code from mspgcc v3.x to v4.x and came across missing macro GET_FRAME_ADDR_F(). I was using that to determine from ISR if CPU was sleeping: psr = (int *) GET_FRAME_ADDR_F(__FUNCTION__); if((*psr &amp; (LPM3_bits)) == LPM3_bits) { /* in LPM3 mode */ .... What is the preferred method of doing that with a new toolchain? Thanks, Sergei ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> Sergei Sharonov 2012-05-18T21:19:52 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10559 <pre>Hi Everyone, I finally got around to doing some work towards packaging the uniarch version of mspgcc and friends for Fedora. I'm working on getting them into the Fedora repos, but in the meantime you can grab the RPMs from here: http://users.ecs.soton.ac.uk/rds/rpm/mspgcc-uniarch/ Cheers, Rob ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> Rob Spanton 2012-05-17T21:15:22 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10545 <pre>I'm sorry for bugging people, and I have Googled this question, but the answers I'm finding are really old and I know there are updates to mspgcc since most of the answers were posted.... I am trying to port 3 different programs from IAR to MSPGCC for work. I'm using the latest released version, but 2 of the 3 won't fit even when compiling using optimizations: -mmcu=$(MCU) -g -Os -Wall -fdata-sections -ffunction-sections and linked with --no-keep-memory -Wl,-gc-sections Does anyone have any ideas how I can further optimize the compiler (other than rewriting - which I've been trying to do)? With an MSP430F149 processor, under IAR, the code compiles and links (Code = 45858, data = 3000, CONST=4935) Under GCC, it won't link because '.rodata won't fit into region rom' and rom overflows by 796 bytes. Examining the Map file shows .rodata is 0x1a66 in size, .text is 0xc240 in size, .bss is 0x712 Any ideas how to make the libraries or optimizer make smaller code? adam This email, including any attachments a</pre> Adam Ford 2012-05-16T15:14:52 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10544 <pre>Good Morning. I'm a eletronic technologist, and I have recently stated working with MSP programming. I'm trying to make an Ide for program MSP430 in C language using Eclipse, MSPGCC an MSPDebug. Through reseach I realised that you all works using some of these tools, so I was wondering if you could help me to continue my work. I have already installed the MSPdebug and MSPGCC is already working with Eclipse, but now i don't know which is the best way to proceed to make eclipse program and debug my chip when I click in the debug butom. Could you help me, please? Thanks for the attention. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/________________________________</pre> William Antunes da Maia 2012-05-16T13:46:58 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10540 <pre>Is there any timeline for updated debian or Ubuntu packages based on the current LTS Relaease? The packages available out there are still based on the old 20110612 release. </pre> Hans Henry von Tresckow 2012-05-16T07:56:17 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10537 <pre>Development release 20120514 of mspgcc is now available. This is a development release. It's being made to clear up a few reported issues in 20120425 without announcing any new capabilities. It also incorporates a major rework of the gcc infrastructure that is required because gcc never intended sizeof(void*) to differ from sizeof(void(*)()), and generally isn't prepared to deal with pointers of different sizes. The patch bundle for 20120514 is available at: https://sourceforge.net/projects/mspgcc/files/mspgcc/DEVEL-4.7.x The tag workspace/release/20120514 in git://mspgcc.git.sourceforge.net/gitroot/mspgcc/mspgcc checks out a workspace configured for this release. The tag workspace/master checks out a workspace configured for the development series. Downstream packagers: please don't bundle this. It's so experimental, only people who are build from source should be playing with it. The stable series remains LTS-20120406. As usual, please submit problems as tracker tickets at: https://sourceforge.</pre> Peter Bigot 2012-05-15T02:12:24 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10535 <pre>Dear all, Is it really intended that ptrdiff_t is 32bit? I guess not, because the "gcc47: 20-Bit Design" states: "Memory model target options are accepted only when building for CPUX-capable MCUs. Compilation for non-CPUX MCUs effectively uses the small memory model." And before that about the small memory model was stated: "size_t and ptrdiff_t are 16 bits, and no data object may exceed 32767 bytes." I am referring to mspgcc-20120406-p20120502 (non-CPUX) For a quick check how msp430-gcc is configured: $ msp430-gcc -dM -E - &lt; /dev/null | grep PTRDIFF #define __PTRDIFF_MAX__ 2147483647L #define __SIZEOF_PTRDIFF_T__ 4 #define __PTRDIFF_TYPE__ long int In contrast to the AVR gcc: $ avr-gcc -dM -E - &lt; /dev/null | grep PTRDIFF #define __PTRDIFF_MAX__ 32767 #define __SIZEOF_PTRDIFF_T__ 2 #define __PTRDIFF_TYPE__ int I came across this issue when looking at the generated code for int pointer subtraction. Surprisingly huge code, because a sign extension and a 32bit subtraction was performed. However when dealin</pre> Guido Muesch 2012-05-14T21:19:00 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10532 <pre> hello everyone, i've been trying to move from the old mspgcc4 version to the current LTS one for an on-going project, but there is a problem at the final link stage : __udivmodsi4 is missing for vuprintf /opt/mspgcc/lib/gcc/msp430/4.6.3/../../../../msp430/lib/libc.a(vuprintf.o): In function `vuprintf': /mspgcc/msp430-libc-20120224/src/./stdlib/vuprintf.c:549: undefined reference to `__udivmodsi4' /mspgcc/msp430-libc-20120224/src/./stdlib/vuprintf.c:549: undefined reference to `__udivmodsi4' /mspgcc/msp430-libc-20120224/src/./stdlib/vuprintf.c:552: undefined reference to `__udivmodhi4' /mspgcc/msp430-libc-20120224/src/./stdlib/vuprintf.c:552: undefined reference to `__udivmodhi4' this symbol can be found in gcc-4.4.5/gcc/config/msp430/libgcc.S in the old mspgcc4 source that i built some time ago, but not any more in the new version based on 4.6.3, although the symbol appears in many object files of the msp430-libc btw, i followed these directions to build the tool chain http://sourceforge.net/apps</pre> Franck Rousseau 2012-05-11T13:46:27 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10531 <pre>Hi, Did anyone tried to install and use the binutils, especially the msp430-objcoy on a sheevaPlug (Plug computer - ARM based)? The armel distribution binaries fail with seg fault.... - Tal ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> Tal Anker 2012-05-10T12:14:30 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10529 <pre>Hello, Using tutorials on net, i tried to install msp430-gcc. these are the steps i did: 1)sudo apt-get install subversion gcc-4.4 texinfo patch libncurses5-dev zlibc zlib1g-dev libx11-dev libusb-dev libreadline6-dev 2)svn checkout https://mspgcc4.svn.sourceforge.net/svnroot/mspgcc4 3)cd mspgcc4 4)sudo ./buildgcc.sh 5)I accepted all the the default (no selection) until i'm asked to start the build [default NO], i did yes: then i get this error: config.status: executing default commands make[2]: entrant dans le répertoire « /mspgcc4/build/binutils-2.20.1-build/bfd » Making info in doc make[3]: entrant dans le répertoire « /mspgcc4/build/binutils-2.20.1-build/bfd/doc » make chew make chew make[4]: entrant dans le répertoire « /mspgcc4/build/binutils-2.20.1-build/bfd/doc » make[4]: entrant dans le répertoire « /mspgcc4/build/binutils-2.20.1-build/bfd/doc » make[4]: « chew » est à jour. make[4]: « chew » est à jour. make[4]: quittant le répertoire « /mspgcc4/build/binutils-2.20.1-build/bfd/</pre> asma bel hadj med 2012-05-08T21:47:34 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10517 <pre>We have an older project at my work where we use the TI BSL loaded to load code over RS-232. Our code is broken up into two categories a configuration file and a firmware file and they are both loaded together. The configuration file is a list of constants stored in flash and specific addresses and they are unique for each of our customers, but the firmware file is the same. The code we have now was written with IAR, and I'm trying to port it over to mspgcc. What I'd like to be able to do is compile the firmware with the linker script specifying certain addresses of data, but I don't want the compiler to actually put any data at those locations. For the configuration, I'd like to just compile the constant variables without firmware. The problem I see is that GCC initializes the constant variables in the FW which I have to go and manually delete because those constants are loaded from a separate txt file. I'd like to have that more streamlined technique to build both. Any ideas on the best way to do t</pre> Adam Ford 2012-05-04T19:38:04 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10516 <pre>Hello, Is there any known issues where MSPDebug in Windows (compiled in cygwin with mingw and ran with cygwin) would throw a segmentation fault when issuing "mspdebug.exe rf2500 erase 'prog bin.elf' "? If not, what could be the problem? I have tried looking for this in Google, but couldn't find anything related. I don't have the actual output here, it happened to someone during a workshop I was doing to get some guys started with the Launchpad, but I can ask him to run some commands. Best regards, --------------------------------------- Sergio Campamá sergiocampama&lt; at &gt;gmail.com ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ </pre> Sergio Campamá 2012-05-04T13:07:11 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10514 <pre>The first set of patches for LTS release 20120406 is now available on SourceForge at http://sourceforge.net/projects/mspgcc/files/Patches/LTS/20120406/ Neither of these are particularly critical, unless you run into them. Downstream packagers: Please note the text in the README at http://sourceforge.net/projects/mspgcc/files/Patches/LTS/ regarding how to mark patched releases of mspgcc. This is the first release to which this practice applies; if you have problems with it, let me know. msp430-libc-20120224-sf3522752 "malloc return null problem" (https://sourceforge.net/tracker/?func=detail&amp;aid=3522752&amp;group_id=42303&amp;atid=432701) malloc() may fail to detect when it has run out of memory, and may end up overwriting the call stack. It would also use memory that was reserved for no-init sections. This bug is likely to have been present for as long as msp430-libc has existed. msp430mcu-20120406-sf3522088 "msp430mcu install.sh misses a mkdir" (https://sourceforge.net/tracker/?func=detail&amp;aid=3522088&amp;group_</pre> Peter Bigot 2012-05-02T18:42:06 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10507 <pre>Hi, I have been doing a bit of work on MSPDebug over the weekend trying to figure out a few issues I've been having. The one problem I can't solve is when using msp430-gdb and mspdebug, the code executes about ten times slower than it should (when using the new tilib driver which makes use of TI's new MSP430.dll v3). During my testing I have determined that following a call to MSP430_Memory(....., READ); the execution speed will be slow. The first thing GDB does when connecting to the target is read the memory at the PC, which means it will always run slow after that. MSPDebug will run slow after the first run, ctrl+c combination, as it will read and disassemble the current function when you press ctrl+c. I am on windows 7 32bit using version 3.2.3.15 of msp430.dll (from msp430.dll_developer_package_rev_3.02.003.015.zip). I was wondering if anybody had run into similar issues? I will try duplicating the issue on my work PC tomorrow before I start making noise in the E2E forums. Thanks, - Wa</pre> Wayne Uroda 2012-04-29T13:52:37 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10500 <pre>Hi After updating from the 2011 LTS to the new LTS version, my code to place a 10k array into . fartext section fails. The source file looks like this: __attribute__((section (".fartext"))) const uint8_t cc256x_init_script[] = { 0x00, ... roughly 10k of data ... }; const uint32_t cc256x_init_script_size = sizeof(cc256x_init_script); I get this error: msp430-gcc -mmcu=msp430f5438a -g -Os -Wall -I. -I../src -I../firmware -I../.. -I../../chipset-cc256x -I../../src -I../../include -c -o ../../chipset-cc256x/bluetooth_init_cc2560A_1.7.o ../../chipset-cc256x/bluetooth_init_cc2560A_1.7.c msp430-gcc ../../chipset-cc256x/bluetooth_init_cc2560A_1.7.o main.o -mmcu=msp430f5438a -o led_counter.out ../../chipset-cc256x/bluetooth_init_cc2560A_1.7.o:(.debug_info+0x8e): relocation truncated to fit: R_MSP430_16_BYTE against symbol `cc256x_init_script' defined in .fartext section in ../../chipset-cc256x/bluetooth_init_cc2560A_1.7.o collect2: ld returned 1 exit status Is there something I'm doing wrong, or, is this a r</pre> Matthias Ringwald 2012-04-27T19:19:54 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10491 <pre>The first draft of the design specification for 20-bit support in mspgcc has been added to the wiki at: https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Gcc47:20-Bit_Design Interested parties are invited to read the document on the wiki, and comment on this mailing list. The specification focuses on the atomic capabilities which combine to form what's normally called a "memory model". They are highly orthogonal, although some combinations are likely to result in unexpected (i.e., buggy) behavior. I specifically invite comment on exactly what memory models should be supported by roll-up options that enable/disable the individual features described on that page, and what compiler option will identify them. (It'd be something like "-mmodel=large", but what exactly should "large" mean?) Preferably the naming and semantics of these models should tie back to existing practice in other MSP430 toolchains or other GCC back-ends. At this time, I believe what's described is technically possible, bu</pre> Peter Bigot 2012-04-26T21:31:19 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10490 <pre>Development release 20120425 of mspgcc is now available. This is a development release. It begins the path to 20-bit support by adding int20_t and uint20_t: these are implemented under the covers by a new type attribute __a20__ which indicates that the 32-bit type it attaches to maintains only 20 bits of precision, uses a single 20-bit register, but two words when placed in memory. It is available via &lt;stdint.h&gt; when compiling with -mcpu=430x (which is implied by any -mmcu option that identifies a 430X CPU). The purpose of this type is primarily to simplify validation of the sorts of operations that will be needed for 20-bit pointers, but it may also come in handy when a little extra precision is required. An example of use: #include &lt;inttypes.h&gt; #include &lt;stdio.h&gt; uint16_t vals[] = { 1, 2, 3, 4, 5, 6, 7, 8, 9, 0x8001, 0x8002, 0x8002, 0x8004, 0x8005, 0xf000 }; void main (void) { int i; uint20_t sv; sv = 0; for (i = 0; i &lt; sizeof(vals)/sizeof(*vals); ++i) { sv += vals</pre> Peter Bigot 2012-04-25T14:56:44 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10476 <pre>Howdy. I recently ran into an issue with my program stack growing into the statically-allocated variables in the .bss section due to some overenthusiastic use of printf's. Looking through the archives, I found this discussion&lt;http://www.mail-archive.com/mspgcc-users&lt; at &gt;lists.sourceforge.net/msg10178.html&gt; regarding general stack protection techniques. Two questions, which may be more general gcc/ld-related than msp-specific 1. While it's impossible in the general case to determine the maximum stack size that a program will use, is there any mspgcc setting (or standalone tool) that can handle the simple cases that dominate in MCUs (no recursion, no function pointers, no nested ISRs) and spit out a maximum stack depth? 2. Failing that, what is the preferred method for indicating that X bytes should be reserved at the top of RAM, and violations of this should result in a linker error? It looks like the .noinit section gets placed where I want it, so I see a couple of options: a. Use the RESERVE_RAM annotation</pre> Doug Carlson 2012-04-19T12:37:00 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10462 <pre>Hi, I feel quite foolish asking the following question... Please don't judge me too harshly... In my MSPGCC based system I have got the following #defines which I use for critical (interrupts disabled) access around volatile memory which is modified by interrupt routines: #define criticalStart() __asm__ __volatile__("push r2"::); __asm__ __volatile__("dint"::) #define criticalEnd() __asm__ __volatile__("pop r2"::) Usually I use this code to write to a counter which is decremented by my timer ISR, eg void setTimeout(UInt16 timeout) { // Other work before setting the volatile, ISR driven value criticalStart(); busyTimeout = timeout; criticalEnd(); } Today I am using Code composer for a new project and I tried a similar trick. After several hours of debugging, it turns out that my little "push r2" trick causes code composer to access local variables incorrectly, since these are accessed relative to the stack pointer. For example, the following code does not function correctly because the </pre> Wayne Uroda 2012-04-17T07:53:08 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10457 <pre>I'm pulling out my hair (and I don't have much to lose) trying to get mspdebug to talk to a MSP-EXP430F5438 experimenter board through TI's MSP-FET430UIF. Here's what I'm getting: $ MSPDEBUG_TI3410_FW=/opt/local/lib/mspdebug/ti_3410.fw.ihex mspdebug -d /dev/tty*FET* uif MSPDebug version 0.19 - debugging tool for MSP430 MCUs Copyright (C) 2009-2012 Daniel Beer &lt;dlbeer&lt; at &gt;gmail.com&gt; This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open UIF on /dev/tty.MSP-FET430UIF26230... Initializing FET... FET protocol version is 20401000 Configured for Spy-Bi-Wire Set Vcc: 3000 mV fet: FET returned error code 4 (Could not find device (or device not supported)) fet: command C_IDENT1 failed fet: identify failed Trying again... Initializing FET... FET protocol version is 20401000 Configured for Spy-Bi-Wire Sending reset... uif: read error: Operation timed out warning: fet: reset failed uif: read error: Operation tim</pre> Andy Turk 2012-04-15T18:14:21 http://comments.gmane.org/gmane.comp.hardware.texas-instruments.msp430.gcc.user/10455 <pre>Hi all, TI has recently updated their driver which can be downloaded here: http://processors.wiki.ti.com/index.php/MSP_Debug_Stack You will get now the file slac460b.zip (instead of slac460a.zip) and it refers to the firmware version 3.2.3.15. The new version still needs a patch on 64Bit systems but I could build it without the patch on a 32Bit System. The patch and the project files can be downloaded here: http://sourceforge.net/projects/msp4linux/files/ The msp4linux project was updated to support the new lib and there is a feature back which was once removed with the change from 0.3.0 to 0.4.0: the device database extractor. The v3 driver stores a lot of information about all supported targets in a internal database which is located in .../DLL430_v3/src/TI/DLL430/TemplateDeviceDb The database extractor tool creates a library which can be used to list this information. Type simply 'info' to get the data from the attached target or info [name] to get it for other targets: mspdb_v3$ info MSP430F5</pre> qbert1< at >gmx.de 2012-04-12T20:12:30 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.hardware.texas-instruments.msp430.gcc.user