hi folks, last summer (july 2010) i bought a ti eval board for the 5438 and proceeded to pull together and test the dirt-simple devel pieces before proceeding on to trying to work with tinyos on this mcu.
short story is that is used the then-current mspgcc4; wrote my own bsl so that i had a boilerplate for modding tos-bsl to support this mcu; wrote a ~25-line blink in c to test it. result: i could compile, objcopy -> ihex, bsl, and execute blink on the little eval board. nothing elaborate or fancy: msp430-gcc -mmcu=msp430x5438 -o blink.exe blink.c msp430-objcopy --output-target=ihex blink.exe blink.ihex bsl /dev/ttyUSB0 blink.ihex happiness, now i could try out real stuff. then i got sidetracked until now. following all of work of peter bigot, eric decker, razvan, et. al on the uniarch toolchain, i pulled the latest assembled bits (most easily from tinyprod.net, thanks guys) and went back to step one. after the requisite header/prototype changes to blink.c, everything seems to work properly, except that the code doesn't run. (yes, i can install the old ihex and make the board blink again). a quick comparison of the working ihex file with the new one i see that they're vaguely similiar, the addresses/sizes of the code/vectors seem right, but... i did try adding the -mcpu=430xv2 flag to the compile line, but that makes no difference in the ihex. can anyone please offer a pointer on how to proceed? thanks, steve ayer ------------------------------------------------------------------------------ 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. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
