Re: [Mspgcc-users] TI compiler
On 23/03/17 15:10, David W. Schultz wrote: > The family guides have complete descriptions. In this case slau144. Thanks David, I seem to have missed that, it is indeed a proper description. Thanks for all the help. The TI compiler is still no good - the interrupts are still taking much longer that the old compiler and the code size is still much bigger. The enhancements that I wanted to do to the target can, seemingly, only be achieved with the old compiler at this time. I'll give up on the TI one and keep looking in case it improves. Cheers, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 23/03/17 11:45, David W. Schultz wrote: > While you didn't explicitly call a function in your interrupt routine, > the compiler did for the right shift of TXByte. Which the 'old' compiler doesn't. And your complaint to TI of April 2015 appears to have been ignored. > Making TXByte a signed int makes this go away. (The MSP430 doesn't have > a single instruction to do the unsigned right shift.) You don't need for > it to be unsigned because you don't care about those bits. In this case, true, but irritating. > A minor nit: > > Making TXByte and BitCnt volatile buys you nothing except slower code. Yes, I forgot to remove this. It was just an attempt to try to influence the compiler. Is there any way of inputting this to TI? and Do you know where there is proper documentation of their instruction set? What I have from TI is scant, to say the least. Thanks, Bob -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
OK,
here is some code that shows the problem.
I use OpenSUSE LEAP 42.1 as the operating system and have both compilers
installed in /opt under 2 different names ("msp430-elf-gcc" for the TI
and "msp-gcc" for the 'old' P.A.Bigot compiler).
Hope it's not too much, I've tried to keep it as small as reasonable
without hiding anything.
The source:
/*
**
**
Compiler test: msp430-elf-gcc
Includes and Interrupt definition syntax different for 'old' mspgcc
Otherwise identical
**
**
*/
#include
#include
/*
**
Programmer information *** DO NOT USE IFDEFS *** (AWK'ed by avrprog etc)
OK to comment out with '//'
**
*/
#define MCU_TARGET msp430g2232
#define LED BIT0// LED on P1.0
#define TXD BIT1// TXD on P1.1
#define RXD BIT2// RXD on P1.2
#define Bit_time104 // 9600 Baud,
SMCLK=1MHz (1MHz/9600)=104
#define Bit_time_5 52 // Time for
half a bit.
volatileuint16_tBitCnt; // Bit count,
used when transmitting byte
volatileuint16_tTXByte; // Value sent
over UART when
put_char() is called
uint16_tresult, status, checksum;
/*
**
Write a character to RS232
**
*/
static void put_char(uint8_t databyte)
{
TXByte = databyte;
TXByte |= 0x100; // Add stop bit
(= 1)
TXByte <<= 1; // Add start
bit (= 0)
BitCnt = 10; // Load Bit
counter, 8 bits + start + stop
P1OUT |= TXD;
TACTL = TASSEL_2 + MC_2; // SMCLK,
continuous mode
TACCR0 = TAR; // Initialize
compare register
TACCR0 += Bit_time;// Set
time of first bit
TACCTL0 = CCIE; // Enable
interrupts
while (TACCTL0 & CCIE ) {};// Wait
for TX completion (by the
interrupt)
}
/*
**
Main
**
*/
void main(void)
{
WDTCTL = WDTPW | WDTHOLD; // Stop WDT
BCSCTL1 = CALBC1_1MHZ; // Set range
DCOCTL = CALDCO_1MHZ; // SMCLK = DCO
= 1MHz
P1DIR |= TXD | LED;
_NOP();
_EINT(); // interrupts
enabled
while(1)
{
put_char('+');
}
}
/*
**
Timer A0 interrupt service routine (RS-232 9600 Baud Tx).
Handles Tx bit timing.
**
*/
void __attribute__ ((interrupt (TIMER0_A0_VECTOR))) TIMER0_A0_ISR(void)
{
P1OUT &= ~LED; // Turn LED on
(start of interrupt)
TACCR0 += Bit_time;// Add
Offset to TACCR0
if (BitCnt == 0) // If all bits
TXed
{
TACTL = TASSEL_2; // SMCLK
selected, timer off (for power
consumption)
TACCTL0 &= ~CCIE ; // Disable
interrupt
}
else
{
if (TXByte & 0x01)
P1OUT |= TXD;
else
P1OUT &= ~TXD;
TXByte >>= 1;
BitCnt--;
}
P1OUT |= LED; // Turn LED on
(end of interrupt)
}
The compile command for msp430-elf-gcc (taken from running my 'make').
msp430-elf-gcc -I/opt/msp430-gcc/include/ -O2 -Wall -g -mmcu=msp430g2232
-Wno-main
Re: [Mspgcc-users] TI compiler
On 22/03/17 16:24, David W. Schultz wrote: > Calling another function from the ISR was what triggers this bad > behaviour. Especially if the called function is in another file. Hi David, my code doesn't call a function in the interrupt, it merely decrements a count, tests it for zero and, if not, sets a port bit hi or low, then exits. This uses only R13 which is why I'm surprised that all the others are 'push-pulled'. Your description also depicts not the best behaviour. Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 06/03/17 21:53, David W. Schultz wrote: > On 03/06/2017 02:19 PM, Bob von Knobloch wrote: >> Hi David, >> How have you extracted these from the .elf file? > > I didn't. You were talking about the .hex file so that is where I looked. > > The ISRs start out like this: > > __attribute__((wakeup, interrupt(USCI_A1_VECTOR))) void rxISR(void) > OK - I have it now, You put me on the right track David. I have been used to creating the hex file with "objcopy", in a make file. For my AVR projects, this copied .text, .data, & .vectors into the HEX output. It seems this is unnecessary with msp430-elf-gcc and a simple "objcopy" from "main.elf" to "main.hex" with no section options does the job, also including the used ISRs and reset vectors. Many thanks, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 06/03/17 21:53, David W. Schultz wrote: > On 03/06/2017 02:19 PM, Bob von Knobloch wrote: >> Hi David, >> How have you extracted these from the .elf file? > > I didn't. You were talking about the .hex file so that is where I looked. > > The ISRs start out like this: > > __attribute__((wakeup, interrupt(USCI_A1_VECTOR))) void rxISR(void) > Thanks David, I have 2 ISRs in my file. Their .text parts appear in the output, but the appropriate vector entries are missing. The compiler does not make a hex file. This is done by objcopy. Somewhere in your compile command (Makefile?), there is a stanza like "msp430-elf-objcopy -j text -t data -j vectors -O ihex" or similar. This places the vectors in the hex file (or, in my case, it doesn't). If you can find this, I would appreciate a look at it. Regards, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 06/03/17 18:09, David W. Schultz wrote: > On 03/06/2017 10:25 AM, Bob von Knobloch wrote: >> Now I have to find out where the vectors have gone - they are missing >> from the .hex file. Maybe a different name from the old mspgcc? >> > > TI moved a lot of things into the linker scripts a while back. Each > vector now gets its own section and as near as I can tell, these will > not appear in the output unless you have an actual ISR defined. > > I have three interrupt service routines in the program I am using as an > example and the hex file includes this: > > :02FFE6001259AE > :02FFEA00A883EA > :02FFF400EE55C8 > :02FFFE006A5245 > > I count three interrupt vectors plus reset. > Hi David, How have you extracted these from the .elf file? I have no vectors, not even reset (and there are 2 ISRs defined): Regards, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 06/03/17 17:52, DJ Delorie wrote: > > Bob von Knobloch <b...@vknobloch.de> writes: >> Now the linker doesn't want to play with me - it cannot find the >> "msp430g2231.ld" link file. Curious because the compiler fids "msp430.h" >> in the same directory. > > Add "-v" to your gcc line, it will show you more info on where it's > searching for things. Note that the linker and the preprocessor use > different search paths; the path to the linker script may come from gcc > (via -L or an absolute path) or from the linker's built-in path. > > You can also use "strace -f -o /tmp/foo gcc . . ." to capture all the > places it searches for files (grep for msp430g2231 in that file), which > might help. > Thanks DJ, the -v flag is very useful. I solved this problem by moving the -ld scripts. Now I must find the vectors which do not appear in my hex file. Regards, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 06/03/17 16:58, Ben Green wrote: >>From my understanding the .h files and the .ld files are not supposed to be >>in the same directory. When in installed msp430-gcc-support-files-1.198.zip I >>did this: Curious, as the TI installer places them there (under /opt/msp430-gcc/include) > cp *.ld /opt/msp430-elf-6.2.1.16/msp430-elf/lib/430/ > cp *.h /opt/msp430-elf-6.2.1.16/msp430-elf/include/ Makes sense - I'll try that. > Now that does seem strange, I would have expected that to work, did you make > sure you were passing the argument to the linker and not GCC (though that > might not make any difference)... how about using the -L switch? > > -L /opt/msp430-elf-6.2.1.16/msp430-elf/lib/430 -T msp430g2231.ld Yes, tried that too. > Benjamin. Yes, splitting the two worked, (I wonder why they installed into the same place?) thank you Ben. From David Schultz, > I include -Wl,-L$(SUPPORT_FILE_DIRECTORY) in the flags for gcc when > linking. I had tried this, but no joy. Now I have to find out where the vectors have gone - they are missing from the .hex file. Maybe a different name from the old mspgcc? Cheers, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Announcing the Oxford Dictionaries API! The API offers world-renowned dictionary content that is easy and intuitive to access. Sign up for an account today to start using our lexical data to power your apps and projects. Get started today and enter our developer competition. http://sdm.link/oxford ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 03/03/17 19:30, DJ Delorie wrote: > Also, you can use "msp430-elf-gcc -mintr ..." to minimize the runtime > support. Thanks DJ, I tried -mintr and at least one project produces code that could fit, thanks (should have RTFM - but finding this was not intuitive). Now the linker doesn't want to play with me - it cannot find the "msp430g2231.ld" link file. Curious because the compiler fids "msp430.h" in the same directory. It looks like the dir info is not being passed to the linker. I have tried forcing it with -T, but no joy. I have my compiler installed at /opt/msp430-gcc/ (I don't want to clutter /usr/local/bin) and wonder if a hard coded path has been set somewhere? I am running on OpenSUSE42.1 (which is 64-bit). I have tried compiling from source and also installing TI's installer - the results are the same. Any one have any ideas ? Regards, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 03/03/17 19:30, DJ Delorie wrote: > > This has come up before, and here's what's going on... the new > msp430-elf-gcc includes all the code required by the standard, partly > because... well, standards... > So you end up with things like "argv handling" when there's no command > line, or "exit closes files" when you never exit. A big change is using > a float-enabled printf when you don't need it. > > > Also, you can use "msp430-elf-gcc -mintr ..." to minimize the runtime > support. > > Also, if you're REALLY constrained to size, you might consider getting > the crt0.S source file from newlib and modifying it yourself to really > strip out the parts you don't need. Most embedded code really only > needs to set up the stack and watchdog, then jump to main(). > Thanks to all for the input. This confirms what I suspected regarding newlib. I will pursue rewriting crt0.S at some stage. For now, I still can go back to an old OS with mspgcc as a stopgap. Cheers, Bob -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] TI compiler
On 03/03/17 14:29, David W. Schultz wrote: > On 03/03/2017 05:20 AM, Bob von Knobloch wrote: >> As far as I can see, the 'bloat' is in library funcs (newlib?). >> Why the 50% increase and can I mitigate this somehow? >> Regards, >> Bob von Knobloch. >> > > Hard to say without seeing the code. Have you looked at the resulting > file using objdump? If not, that can disassemble the code into something > readable so you can see just what is going on. > Yes, it shows (as does the .map file) that the .text corresponding to my source is approx. the same size for both compilers, but that the very basic library functions that get pulled in (add, subtract etc.) are producing much more code than in the old version. I have tested different optimisation switches, but always get the same resulting code size. Bob -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] TI compiler
Hi, I've been using the 'old' compiler last maintained by P.Bigot(many thanks to him). Now I need to make some changes and have installed the new msp430-gcc 6.2.1.16 under OpenSuse 42.1 My small project under the 'old' compiler produced a .text size of 1392 bytes, the 'new' compiler makes a .text of 2160 bytes. This no longer fits on the target µproc. As far as I can see, the 'bloat' is in library funcs (newlib?). Why the 50% increase and can I mitigate this somehow? Regards, Bob von Knobloch. -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] Toolchain build
Hi, I am trying to build the toolchain, following the wiki Install:from source in order, as it is written. On OpenSUSE 12.1 32-bit. The make of gcc is crashing with: = make[2]: Entering directory `/mnt/local/Downloads/msp430/gcc-4.6.3/msp430/libgcc' Makefile:156: ../.././gcc/libgcc.mvars: No such file or directory make[2]: *** No rule to make target `../.././gcc/libgcc.mvars'. Stop. make[2]: Leaving directory `/mnt/local/Downloads/msp430/gcc-4.6.3/msp430/libgcc' make[1]: *** [all-target-libgcc] Error 2 make[1]: Leaving directory `/mnt/local/Downloads/msp430/gcc-4.6.3' make: *** [all] Error 2 = I notice that in some places gcc-core-4.6.3.tar.bz2 is mentioned and in others gcc-4.6.3.tar.bz2 so I tried both but get identical errors. I executed: cd gcc-4.6.3 ./contrib/download_prerequisites as the prerequisites aren't listed on the wiki page, could it be that something is missing? I don't know what mvars does. I would appreciate any tips. Bob von Knobloch -- The Sun is out, the sky is blue, it's time to drive the MR2. -- 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/ ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] Toolchain build
On 07/07/12 17:14, Peter Bigot wrote: Yes, the ability to read what is written is sometimes an advantage. Thanks for the correction. All compiled except mspdebug, but I'll look into that later. Bob The paths in the log you quote suggest you're building from within the source directory. This is not allowed by gcc anymore. I did not contribute the wiki page, but the script there seems to do it right: #Configure GCC cd ../gcc-4.6.3-msp430 ../gcc-4.6.3/configure --target=msp430 --enable-languages=c --program-prefix=msp430- make Peter On Sat, Jul 7, 2012 at 10:09 AM, Bob von Knobloch b...@vknobloch.de wrote: Hi, I am trying to build the toolchain, following the wiki Install:from source in order, as it is written. On OpenSUSE 12.1 32-bit. The make of gcc is crashing with: = make[2]: Entering directory `/mnt/local/Downloads/msp430/gcc-4.6.3/msp430/libgcc' Makefile:156: ../.././gcc/libgcc.mvars: No such file or directory make[2]: *** No rule to make target `../.././gcc/libgcc.mvars'. Stop. make[2]: Leaving directory `/mnt/local/Downloads/msp430/gcc-4.6.3/msp430/libgcc' make[1]: *** [all-target-libgcc] Error 2 make[1]: Leaving directory `/mnt/local/Downloads/msp430/gcc-4.6.3' make: *** [all] Error 2 = I notice that in some places gcc-core-4.6.3.tar.bz2 is mentioned and in others gcc-4.6.3.tar.bz2 so I tried both but get identical errors. -- The Sun is out, the sky is blue, it's time to drive the MR2. -- 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/ ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] Vector Problems with processor type
Hi, I'm using mspgcc 20110716. I have a project using an msp430g2231, which compiles and runs OK. I am trying to change to processor type to a g2232 or g2332. When I specify one of these (e.g. -mmcu=msp430g2232) then the toolchain (linker) reports: msp430-gcc -Wall -g -Os -mmcu=msp430g2232 -Wno-main -c -o mspsani.o mspsani.c mspsani.c: In function ‘TIMERA0_ISR’: mspsani.c:343:27: error: interrupt vector 538631144 is beyond end of MCU vector table make: *** [mspsani.o] Error 1 I have looked at the library headers for these devices and everything looks sane. Can anyone suggest why the offset for the vector table appears wrong with these devices? -- The Sun is out, the sky is blue, it's time to drive the MR2. -- Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] MSP430 Device ID Bytes
This is a little off-topic I'm afraid, but I can't find any information and don't know here better to ask. I am writing a programmer for MSP430 chips, using an AVR ATMega (requirement, due to existing equipment). I would like to check that the target is the right part (AVRs have well documented serial numbers). I see that the MSP430 parts also have device IDs but I can't find any reliable information about them. The TI docs seem to be outdated or incomplete. Can anyone point me to a better source of information? Many thanks, Bob von Knobloch -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSP430 Device ID Bytes
On 01/12/11 14:46, Mitnacht, Thomas wrote: Does this help? http://processors.wiki.ti.com/index.php/REP430F http://www.ti.com/tool/rep430f Regards, Thomas Mitnacht Thanks Thomas, I have this, but it seems incomplete, maybe I am expecting too much :-) Bob -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSP430 Device ID Bytes
On 01/12/11 15:15, Peter Bigot wrote: I don't remember where I found this information, but I believe most chips have a block of data at 0x0FF0 which contains chip-specific information that can be used to figure out the part number. Other data lives in the infoA segment of some chips, and in a separate TLV (tag-length-value) section in the 5xx/6xx series. Addresses for those segments are device-specific, though I think there might be a pointer to the TLV section in the block at 0xFF0. I'm unaware of any available machine-readable map from magic numbers at block 0x0FF0 to device identifiers, or identification of which TLV tag pertains to which peripheral. I am aware that peripherals like the ADC12 have different TLV tags on different MCUs within the same family (or, at least, several value-line devices came with inconsistent TLV tags for ADC). Peter Yes, there are various mentions in various docs, but no concrete cross-reference it would seem. Oh well, I'll build my own little database. Thanks, Bob -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSP430 Device ID Bytes
On 01/12/11 15:27, Mitnacht, Thomas wrote: Hi Bob, What details are you missing? Thanks, Thomas Mitnacht I was hoping to be able to identify the part (or, at least, the flash start address which I need for programming). The SLAU320c doc only maps 3 bytes (0xff0, 0xff1 0xffd) to several families of parts (F20x2 G3x2x Parts) and not distinct models. I expect I must do it myself with a small list. Thanks for helping, Bob -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSP430 Device ID Bytes
On 01/12/11 16:33, Mitnacht, Thomas wrote: Bob, You are right, SLAU320 already talks about how to identify a derivative. The related memory configuration needs to read from the device datasheet. We are working on a machine readable database as part of our debug stack, but this will not be available until m/o next year. Thanks, Thomas Mitnacht Hmm, I could not find any relevant information in the device datasheets (I have studied: MSP430G2231, 2232 2332), or are you building your database from other sources? Thanks to you too, Bob -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSP430 Device ID Bytes
On 01/12/11 17:16, Peter Bigot wrote: I think the point is that, if you already know the device, you can find the address map (from the datasheet, from the msp430mcu package's devices.csv file provided by TI that's used to generate the linker scripts for the toolchain, or from information in the debug DLL package). What's missing is how to figure out what device you have by looking at the MCU boot memory through JTAG/SpyBiWire or at runtime, or some other automated inspection method. I believe mspdebug has performed the MCU identification task by matching FET byte sequences against a database collected from known chips. Perhaps some constants in mspdebug's drivers/fet_db.c are the same as in the 0x0FF0 region. I've wanted to have a routine that could identify the MCU at runtime for a while myself, but the information isn't readily available. Peter Yes, thats exactly what I have been looking for. OK, it's good to know that it doesn't (yet) exist, at least I won't waste time looking further. Many thanks Peter, Bob Mitnacht, Thomas wrote: MSP430G2231 datasheet page 11 should give you what you need Thomas, I think we talked past each other. I know the flash info is there, I wanted a correlation between identity byte(s) and flash size. As Peter confirms, it doesn't exist. Many thanks anyway, Bob -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSPDebug version 0.18
On 07/11/11 22:21, Daniel Beer wrote: MSPDebug version 0.18 is now available from: http://mspdebug.sourceforge.net/download.html Significant new features in this release are: * Support for new chips: MSP430F2121, MSP430F2012, MSP430F449. * Support for raw USB access to FET430UIF and eZ430-F2013. * Support for TI MSP430 library. * Various Win32 bug fixes. * GDB protocol bug fixes. * Section names are displayed when programming. - Daniel Hi Daniel, I cannot get the USB access to work, although programming is working fine. I have a MSP-EXP430G2 (Launch Pad) FET and am running under OpenSuse11.3. --- mspdebug -j uif MSPDebug version 0.18 - debugging tool for MSP430 MCUs Copyright (C) 2009-2011 Daniel Beer dlb...@gmail.com This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. usbutil: unable to find a device matching 0451:f430 --- lsusb only reports a device with 0451:f432 Have you any idea what is wrong ? Thanks, Robert -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSPDebug version 0.18
On 11/11/11 19:48, Chris Liechti wrote: Am 11.11.2011 16:04, schrieb Bob von Knobloch: I have a MSP-EXP430G2 (Launch Pad) FET and am running under OpenSuse11.3. mspdebug -j uif try a different driver i'm using this to download to launchpad: mspdebug rf2500 prog firmware.titext exit chris Yes, this works fine for me Chris. as reported the tool loads programs OK. I'm trying to access the rs232 port (which is supposed to work in 0.18). There, mspdebug 'seems' (in my limited usb experience) to be trying to access the wrong device ID (0451:f430) whereas only 0451:f430 exists, according to 'lsusb'. Thanks for the info, Robert -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] MSPDebug version 0.18
On 11/11/11 20:18, Bob von Knobloch wrote: There, mspdebug 'seems' (in my limited usb experience) to be trying to access the wrong device ID (0451:f430) whereas only 0451:f430 exists, according to 'lsusb'. OOps! Should be: wrong device ID (0451:f430) whereas only 0451:f432 exists Fumblefingers. Sorry, Robert -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
[Mspgcc-users] Build problems
I am trying to build the toolchain on OpenSuse 11.3 Binutils GCC have built OK. (Some trivial thing - in all 3 patch files: ../../binutils-2.21.1/configure. should be: ../../../binutils-2.21.1/configure. or similar). GDB requires: To build, obtain the upstream release distribution from: ftp://ftp.gnu.org/pub/gnu/gdb/gdb-7.2.tar.gz; (From the GDBpatch file) But there is no such version at this URL. There is a gdb-7.2a - is this correct, or is there another source ? Many thanks, Robert von Knobloch. -- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Re: [Mspgcc-users] Toolchain problems
On 22/07/11 12:15, Peter Bigot wrote:
On Thu, Jul 21, 2011 at 11:00 AM, bob b...@vknobloch.de wrote:
I followed the readme exactly. I have what appears to be a sensible
directory structure (although I note the is no 'info' or 'man'
directory, as there was in the '4' version).
If you want those, you have to run the make commands that build and
install them, same as with any other source installation.
main.c:24:16: fatal error: io.h: No such file or directory
I want to correct the paths etc. and will do so once I have built the
tools successfully. Until then can anyone suggest what is wrong here?
No. Find where io.h got put (it comes from msp430mcu), and if it's in
the same place as the other msp430 headers (${prefix}/msp430/include)
figure out what's in your CFLAGS or environment that's keeping it from
being found. If it's not there, figure out what went wrong with the
invocation of install.sh. It may be an Opensuse issue.
I still look forward to your bug report explaining why all the paths are
wrong.
Peter
Thank you, at least I know now where io.h *should* be (and it is).
Is there a doc. outlining the required directory structure anywhere?
And also the location of the correct man/info stuff?
Bob
--
10 Tips for Better Web Security
Learn 10 ways to better secure your business today. Topics covered include:
Web security, SSL, hacker attacks Denial of Service (DoS), private keys,
security Microsoft Exchange, secure Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/
___
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
