> Ok, if I understand correctly, you never get P5.4 and P5.5 set to one?
Yep. I also tried to set breakpoint here. With the same result. > You also have tested enabling interrupts with eint() in main()? (because > in the above version interrupts are disabled and thus the ISR will never > be called...). Also the ISR will only called once. There were some strange things, when I tried to call eint(). The firmware crashed after it. > __low_level_init() and main() are reached? Yes. > What are the actual register > values in gdb if you have reached main(), esp R1 would be of interest. > Have you checked the interrupt vectors at 0xffc0-0xffff? What are they > showing? Ok, I will try to do it in few days. > As stated before from Roberto(?), you have to include the > "msp430x241x.h", not the "msp430x24x.h"! Interrupt mapping is > differently. Tryed them both. There were no significant difference. > Also it would be great, if you lett the compiler run with > "msp430-gcc -v". d...@x200:~$ /opt/mspgcc/bin/msp430-gcc -v Reading specs from /opt/mspgcc/lib/gcc-lib/msp430/3.2.3/specs Configured with: ./configure --target=msp430 --prefix=/opt/mspgcc --disable-multilib --disable-libc --disable-libssp --disable-intl --disable-libiberty --with-gcc --with-gnu-ld --with-gnu-as --with-stabs --disable-shared --disable-threads --disable-win32-registry --disable-nls --enable-languages=c,c++ Thread model: single gcc version 3.2.3 --- Regards, Dmitry > Hardy > > ------------------------------------------------------------------------------ > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users
