Yes - I skipped a fair amount of the code that was in the middle of the
function, since it would make the code snippet far bigger. But I've now
made a test example with pretty much the same effects. The exact registers
used depend on what other variables are declared, and when they are
declared.
Hi,
i want to see what's in the ADC-Memory but the IAR C-Spy can only show
what's in the registers. Is there a way to see what's in the ADC-Memory
with other Debugers?
With gdb, you can write
x /16hx ADC12MEM0
However, your easiest method might be to do something like:
typedef
Dave,
I actually do not know...
You can generate an assembly file -S and -dP options.
You'll see, that every register move being performed to save a value and
clobber this register in the future.
So, in the example below, r8 being used at line 120.
r7 - 169. Instead of using r7, the value
Hi,
mspgcc-users@lists.sourceforge.net schrieb am 18.12.02 10:08:22:
Hi,
i want to see what's in the ADC-Memory but the IAR C-Spy can only show
what's in the registers. Is there a way to see what's in the ADC-Memory
with other Debugers?
With gdb, you can write
x /16hx ADC12MEM0
Dave,
I actually do not know...
You can generate an assembly file -S and -dP options.
You'll see, that every register move being performed to save a value and
clobber this register in the future.
So, in the example below, r8 being used at line 120.
r7 - 169. Instead of using r7, the value
thanks, fixed.
code in cvs.
new win32 build/patch will be on SF within about 6 hours.
~d
On Wednesday 18 December 2002 17:17, Peter Kenyon wrote:
I am using the msp430 tool chain and jolly good it is to. Well done chaps.
BUT I noticed that when I declared an interrupt function
interrupt
David,
yes, there was a 'wakeup return' bug which can appear if the function is
completely empty.
already fixed.
~d
On Wednesday 18 December 2002 17:28, David Brown wrote:
I am using wakeup without any problem - I can see the relevant assembly
instruction generated (right at the end of the
Hello, mspgcc-users! How are you?
There are new files on sourceforge my site:
(1) msp430-gcc-win32-20021219-release1-update.exe
It is service pack for msp430-insight-win32-20021217-release1.exe.
It should be installed OVER installed toolchain!
This file is in package
Ok, it apears I've got a step further after installing the _parjtag.so module
into the correct directory. It is now looking for libc.so.6 which doesn't exist
on NetBSD. For now I've created a softlink to the native libc library which
appears to work. pyJTAG now starts up with the following warning
This happened on FreeBSD when device was not properly configured.
So, I've made a link /dev/parport0 to /dev/ppi0 (do not know which device is
equivalent of ppi0 on NetBSD) and set 0666 permissions for it.
Somehow -l /dev/ppi0 did not work. But I did not check the sources.
(sorry, I'm sooo lazy
10 matches
Mail list logo
