nobo...@web.de wrote:

Hi,

i changed to the examples directory and searched for "dint".
I found

slaa138a/water_meter.s
slaa125a/SLAA125Code.S
slaa123/F149-Voice-demo.S
rawsources/flash.c

-> the critical part begins later below and not right after dint. these are all ok without nop, i think.

pc_keyboard/main.c.

-> probably broken, but see below in the quoted message

By the way: Why are some examples in DOS format and some in UNIX format?

by accident. i fixed a number of files. hope i got all of them

chris

Rolf


mspgcc-users@lists.sourceforge.net schrieb am 22.06.04 23:38:11:

nobo...@web.de wrote:

nobo...@web.de wrote:

i looked into the examples and found no nop after dint. It seems all examples 
with dint are wrong.

which examples? the ones in our CVS?

Yes. These are the only ones i do know for mspgcc.
I have downloaded them via cvs:

cvs -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/mspgcc login
cvs -z3 -d:pserver:anonym...@cvs.sourceforge.net:/cvsroot/mspgcc co docs 
examples gcc gdb gdbproxy hardware htdocs jtag msp430-libc msp430simu packaging 
pybsl pyjtag pyserjtag python serJTAGfirmware ubroff

ok, which ones? there are so many ;-)


it's no requirement to put a nop after dint, any non critical instruction works as well. e.g. the flash write example rawsources/flash.c disables ints, then continues to set up the flash controller before the critical loop or segment erase begins.

maybe the pc_keyboard example is broken, but it does not perfectly anyway, thats the reason it's left out in the installer.

chris


Reply via email to