Hi!
Indeed, the SVSCTL is on address 0x55 on the 16xx too. I found several 'bugs' and inconsistencies in the TI documentaiton itself, placing registers here in the one and there in the other document (and of course only one is true). e.g. PMMIFG on the 54xx located at 0x012A (device datasheet) or 0x012C (family overview peripheral map, which tells the correct location). This happens even after several revisions of the datasheets. So if someone (like me with the 54xx) implements the header files strictly based on the datasheet, bugs beyond a simple typo may happen and are difficutl to track down (it took me several hours to find out why the original TI PMM init code didn't work) Some of the MSPGCC header files have been fixed/updated since the last december build. So check the repository for files younger than 12 months :) As for the included header file: the compiler does not include any header file by its own. The MMCU setting is only to tell the compiler about certain hardware requirements (CPU errata or hardware multiplier or such) and tell the linker which memory map/linker script to use. Which one of the header files is included into the compilation is up to you and your use of the #include preprocessor directive in your .c file. JMGross ----- Ursprüngliche Nachricht ----- Von: Masao Kawamura An: mspgcc-users Gesendet am: 08 Dez 2009 02:13:19 Betreff: [Mspgcc-users] A bug in msp430x24x.h Hi all, I am now working with MSP430F2410 and I think I found a bug in the system header file msp430x24x.h. F24x series has SVSCTL register located at 0x0055, while msp430/svs.h specifies the register to be located at 0x0056 by default. Here is a simple patch to fix the problem. *** msp430x24x_orig.h Tue Dec 8 09:45:34 2009 --- msp430x24x.h Tue Dec 8 09:46:04 2009 *************** *** 41,46 **** --- 41,48 ---- #define __MSP430_HAS_CAPLUS__ #define __MSP430_HAS_ADC12__ + #define __msp430_has_svs_at_0x55 + #include <msp430/mpy.h> #include <msp430/gpio.h> #include <msp430/usci.h> I also noticed that the compiler reads 'msp430x24x.h', NOT 'msp430x241x.h', when I specify -mmcu=msp430x2410. Is this correct behavior? I'm currenly using the binary package 'mspgcc-20091230.exe' and have not checked the latest repository. Sorry in advance if it's already fixed. regards -- ------------------------------------------ Masao Kawamura Wireless Products Division Arrow7 Corporation ------------------------------------------ ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
