2012/7/22 Rick Kimball :
> The following post provides information about an eclipse plugin that
> works with the latest version of eclipse:
Unfortunately, there is no pretty list of peripherals so you will need
to add watch expressions for each peripheral register you are
interested in, which is a
iginal Message-
From: Eric Decker [mailto:cire...@gmail.com]
Sent: Montag, 23. Juli 2012 02:15
To: Kuba
Cc: mspgcc-users@lists.sourceforge.net; Peter Bigot
Subject: Re: [Mspgcc-users] View settings of peripherals in debug
On Sun, Jul 22, 2012 at 2:03 PM, Kuba wrote:
> Dear Peter,
>
> Tha
On Sun, Jul 22, 2012 at 2:03 PM, Kuba wrote:
> Dear Peter,
>
> Thank you for your answer. I do understand that my question only touches
> mspgcc toolchain, however I decided to give it a try since people reading
> this list have also quite some "toolset" knowledge.
>
> Thank you for the __P1DIR h
Dear Peter,
Thank you for your answer. I do understand that my question only touches
mspgcc toolchain, however I decided to give it a try since people reading
this list have also quite some "toolset" knowledge.
Thank you for the __P1DIR hint! It is already close to what I would like,
but is there
On Sun, Jul 22, 2012 at 10:44 AM, Peter Bigot wrote:
> mspgcc as a toolchain does not provide an integrated development
> environment, nor any functionality like you describe. To examine the
> contents of a peripheral register within msp430-gdb you have to
> reference the name with two underscor
The following post provides information about an eclipse plugin that
works with the latest version of eclipse:
http://www.43oh.com/forum/viewtopic.php?f=5&t=1874#p13103
The plugin handles much of this tedious setup for gcc and mspdebug
inside of eclipse.
I've only tried it on linux and it works
mspgcc as a toolchain does not provide an integrated development
environment, nor any functionality like you describe. To examine the
contents of a peripheral register within msp430-gdb you have to
reference the name with two underscores prepended, e.g:
(gdb) x __P1DIR
The sort of thing you desc
Hi,
A bit of a noob question perhaps concerning inspecting the settings of
peripherals during debugging session.
Let me explain: in Code Composer Studio when debugging is launched, you
get a window with a tree of all settings of the chip (like for example
P1OUT or BCSCTL1, etc.). This is quite
