> You need to enable the appropriate peripheral clock before you can
> modify it's registers - that applies both to code and to debugger
> access!
>
This was some months ago and I go the system working, so at some time I
must have enabled the relevant peripheral clocks on the way as you
suggested. It's been a learning curve.
Currently revamping an older design but hope to get back to the STM32
system soon!
--
Mike Perkins
Video Solutions Ltd
www.videosolutions.ltd.uk
Reply by pelrun●May 26, 20132013-05-26
You need to enable the appropriate peripheral clock before you can modify it's registers - that applies both to code and to debugger access!
- James
On Thursday, February 21, 2013 7:06:14 AM UTC+10, Fredxx wrote:
> On 20/02/2013 17:01, Tim Wescott wrote:
>
> > On Wed, 20 Feb 2013 03:16:16 +0000, Fredxx wrote:
>
> >
>
> >> On 20/02/2013 02:07, Tim Wescott wrote:
>
> >>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>
> >>>
>
> >>>> On 19/02/2013 22:30, Fredxx wrote:
>
> >>>>> I can get the build and basic debug working, but wondering if there
>
> >>>>> was any easy way of viewing or manually changing CPU internal
>
> >>>>> registers, such as SPI and GPIO?
>
> >>>>>
>
> >>>>> I'm currently stumped and wondering if this is actually achievable?
>
> >>>>
>
> >>>> It may be bad form to reply to your own question, but the answer is
>
> >>>> here: http://embsysregview.sourceforge.net/
>
> >>>
>
> >>> I think it's just fine -- someone raised a question, someone answered
>
> >>> it.
>
> >>>
>
> >>> If you go asking questions just to answer them -- that's bad form. And
>
> >>> kinda pitiful.
>
> >>>
>
> >>>
>
> >> I am really not that sad. Just spent quite some time hunting for any
>
> >> help on the net, then stumbled across this site.
>
> >
>
> > I know how it goes. Sometimes it seems that you just have to expose your
>
> > ignorance in public, then POOF! the answer drops into your lap.
>
> >
>
>
>
> Well I'm now having problems in changing peripheral registers, or their
>
> memory locations in "memory monitor".
>
>
>
> I make a change and as soon as I hit return the value springs back to
>
> its reset value. Similarly for peripheral register values which
>
> similarly spring back after a step instruction!
Reply by Fredxx●February 25, 20132013-02-25
On 25/02/2013 07:50, David Brown wrote:
> On 22/02/13 15:41, hamilton wrote:
>> On 2/22/2013 6:32 AM, Fredxx wrote:
>>> On 22/02/2013 01:38, Ben Bradley wrote:
>>>> On Tue, 19 Feb 2013 20:07:34 -0600, Tim Wescott
>>>> <tim@seemywebsite.com> wrote:
>>>>
>>>>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>>>>
>>>>>> On 19/02/2013 22:30, Fredxx wrote:
>>>>>>> I can get the build and basic debug working, but
>>>>>>> wondering if there was any easy way of viewing or
>>>>>>> manually changing CPU internal registers, such as SPI and
>>>>>>> GPIO?
>>>>>>>
>>>>>>> I'm currently stumped and wondering if this is actually
>>>>>>> achievable?
>>>>>>
>>>>>> It may be bad form to reply to your own question, but the
>>>>>> answer is here: http://embsysregview.sourceforge.net/
>>>>>
>>>>> I think it's just fine -- someone raised a question, someone
>>>>> answered it.
>>>>>
>>>>> If you go asking questions just to answer them -- that's bad
>>>>> form. And kinda pitiful.
>>>>
>>>> What's terribly, incredibly and truly bad form is asking a
>>>> question, then later posting a short "Never mind, I found the
>>>> answer!" and never to be heard from again.
>>>>
>>>
>>> If I was a spammer, or was involved with any of the projects then
>>> I would agree. But there are many helpful people on Newsgroups
>>> who go out of there way to help others. I wouldn't want to waste
>>> their time if I had already found the answer.
>>
>> Do you think others would have liked to see the answer,
>>
>> even if you did answer it yourself ?
>>
>
> Yes, that's the key point.
>
> People often forget that Usenet archives are a major resource. When
> you google for more specialised problems, it's not uncommon to get a
> Usenet (or mailing list) archive in the result. That's why it's
> important to give the answer, even if no one seems interested at the
> time. And it is also one of the reasons why proper quoting,
> snipping, threading, and posting style (i.e., not top-posting) is
> important for public messages.
>
Many thanks for the sentiments. I had made quite a few searches before
my request trying various keywords suited to my predicament.
It's difficult to know when a question may be seen as being too trivial,
and how much time one should spend looking for a solution before posting
such a question.
My immediate thought was to prevent anyone else from researching the
question after I found an answer. If someone else can make use of this
thread, then all's the better.
Reply by David Brown●February 25, 20132013-02-25
On 22/02/13 15:41, hamilton wrote:
> On 2/22/2013 6:32 AM, Fredxx wrote:
>> On 22/02/2013 01:38, Ben Bradley wrote:
>>> On Tue, 19 Feb 2013 20:07:34 -0600, Tim Wescott
>>> <tim@seemywebsite.com> wrote:
>>>
>>>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>>>
>>>>> On 19/02/2013 22:30, Fredxx wrote:
>>>>>> I can get the build and basic debug working, but wondering if
>>>>>> there was any easy way of viewing or manually changing CPU
>>>>>> internal registers, such as SPI and GPIO?
>>>>>>
>>>>>> I'm currently stumped and wondering if this is actually
>>>>>> achievable?
>>>>>
>>>>> It may be bad form to reply to your own question, but the answer
>>>>> is here: http://embsysregview.sourceforge.net/
>>>>
>>>> I think it's just fine -- someone raised a question, someone
>>>> answered it.
>>>>
>>>> If you go asking questions just to answer them -- that's bad form.
>>>> And kinda pitiful.
>>>
>>> What's terribly, incredibly and truly bad form is asking a question,
>>> then later posting a short "Never mind, I found the answer!" and
>>> never to be heard from again.
>>>
>>
>> If I was a spammer, or was involved with any of the projects then I
>> would agree. But there are many helpful people on Newsgroups who
>> go out of there way to help others. I wouldn't want to waste their time
>> if I had already found the answer.
>
> Do you think others would have liked to see the answer,
>
> even if you did answer it yourself ?
>
Yes, that's the key point.
People often forget that Usenet archives are a major resource. When you
google for more specialised problems, it's not uncommon to get a Usenet
(or mailing list) archive in the result. That's why it's important to
give the answer, even if no one seems interested at the time. And it is
also one of the reasons why proper quoting, snipping, threading, and
posting style (i.e., not top-posting) is important for public messages.
mvh.,
David
Reply by hamilton●February 22, 20132013-02-22
On 2/22/2013 6:32 AM, Fredxx wrote:
> On 22/02/2013 01:38, Ben Bradley wrote:
>> On Tue, 19 Feb 2013 20:07:34 -0600, Tim Wescott
>> <tim@seemywebsite.com> wrote:
>>
>>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>>
>>>> On 19/02/2013 22:30, Fredxx wrote:
>>>>> I can get the build and basic debug working, but wondering if
>>>>> there was any easy way of viewing or manually changing CPU
>>>>> internal registers, such as SPI and GPIO?
>>>>>
>>>>> I'm currently stumped and wondering if this is actually
>>>>> achievable?
>>>>
>>>> It may be bad form to reply to your own question, but the answer
>>>> is here: http://embsysregview.sourceforge.net/
>>>
>>> I think it's just fine -- someone raised a question, someone
>>> answered it.
>>>
>>> If you go asking questions just to answer them -- that's bad form.
>>> And kinda pitiful.
>>
>> What's terribly, incredibly and truly bad form is asking a question,
>> then later posting a short "Never mind, I found the answer!" and
>> never to be heard from again.
>>
>
> If I was a spammer, or was involved with any of the projects then I
> would agree. But there are many helpful people on Newsgroups who
> go out of there way to help others. I wouldn't want to waste their time
> if I had already found the answer.
Do you think others would have liked to see the answer,
even if you did answer it yourself ?
Reply by Fredxx●February 22, 20132013-02-22
On 22/02/2013 01:38, Ben Bradley wrote:
> On Tue, 19 Feb 2013 20:07:34 -0600, Tim Wescott
> <tim@seemywebsite.com> wrote:
>
>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>
>>> On 19/02/2013 22:30, Fredxx wrote:
>>>> I can get the build and basic debug working, but wondering if
>>>> there was any easy way of viewing or manually changing CPU
>>>> internal registers, such as SPI and GPIO?
>>>>
>>>> I'm currently stumped and wondering if this is actually
>>>> achievable?
>>>
>>> It may be bad form to reply to your own question, but the answer
>>> is here: http://embsysregview.sourceforge.net/
>>
>> I think it's just fine -- someone raised a question, someone
>> answered it.
>>
>> If you go asking questions just to answer them -- that's bad form.
>> And kinda pitiful.
>
> What's terribly, incredibly and truly bad form is asking a question,
> then later posting a short "Never mind, I found the answer!" and
> never to be heard from again.
>
If I was a spammer, or was involved with any of the projects then I
would agree. But there are many helpful people on Newsgroups who
go out of there way to help others. I wouldn't want to waste their time
if I had already found the answer.
Reply by Ben Bradley●February 21, 20132013-02-21
On Tue, 19 Feb 2013 20:07:34 -0600, Tim Wescott <tim@seemywebsite.com>
wrote:
>On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>
>> On 19/02/2013 22:30, Fredxx wrote:
>>> I can get the build and basic debug working, but wondering if there was
>>> any easy way of viewing or manually changing CPU internal registers,
>>> such as SPI and GPIO?
>>>
>>> I'm currently stumped and wondering if this is actually achievable?
>>
>> It may be bad form to reply to your own question, but the answer is
>> here:
>> http://embsysregview.sourceforge.net/
>
>I think it's just fine -- someone raised a question, someone answered it.
>
>If you go asking questions just to answer them -- that's bad form. And
>kinda pitiful.
What's terribly, incredibly and truly bad form is asking a
question, then later posting a short "Never mind, I found the answer!"
and never to be heard from again.
Reply by Fredxx●February 20, 20132013-02-20
On 20/02/2013 21:06, Fredxx wrote:
> On 20/02/2013 17:01, Tim Wescott wrote:
>> On Wed, 20 Feb 2013 03:16:16 +0000, Fredxx wrote:
>>
>>> On 20/02/2013 02:07, Tim Wescott wrote:
>>>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>>>
>>>>> On 19/02/2013 22:30, Fredxx wrote:
>>>>>> I can get the build and basic debug working, but wondering if there
>>>>>> was any easy way of viewing or manually changing CPU internal
>>>>>> registers, such as SPI and GPIO?
>>>>>>
>>>>>> I'm currently stumped and wondering if this is actually achievable?
>>>>>
>>>>> It may be bad form to reply to your own question, but the answer is
>>>>> here: http://embsysregview.sourceforge.net/
>>>>
>>>> I think it's just fine -- someone raised a question, someone answered
>>>> it.
>>>>
>>>> If you go asking questions just to answer them -- that's bad form. And
>>>> kinda pitiful.
>>>>
>>>>
>>> I am really not that sad. Just spent quite some time hunting for any
>>> help on the net, then stumbled across this site.
>>
>> I know how it goes. Sometimes it seems that you just have to expose your
>> ignorance in public, then POOF! the answer drops into your lap.
>>
>
> Well I'm now having problems in changing peripheral registers, or their
> memory locations in "memory monitor".
>
> I make a change and as soon as I hit return the value springs back to
> its reset value. Similarly for peripheral register values which
> similarly spring back after a step instruction!
Strange, I deleted all of the old Eclipse and plugins and downloaded
Juno SR1. I copied this over to the preferred directory, installed the
necessary plugins and hey presto it works!!
Reply by Fredxx●February 20, 20132013-02-20
On 20/02/2013 17:01, Tim Wescott wrote:
> On Wed, 20 Feb 2013 03:16:16 +0000, Fredxx wrote:
>
>> On 20/02/2013 02:07, Tim Wescott wrote:
>>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>>
>>>> On 19/02/2013 22:30, Fredxx wrote:
>>>>> I can get the build and basic debug working, but wondering if there
>>>>> was any easy way of viewing or manually changing CPU internal
>>>>> registers, such as SPI and GPIO?
>>>>>
>>>>> I'm currently stumped and wondering if this is actually achievable?
>>>>
>>>> It may be bad form to reply to your own question, but the answer is
>>>> here: http://embsysregview.sourceforge.net/
>>>
>>> I think it's just fine -- someone raised a question, someone answered
>>> it.
>>>
>>> If you go asking questions just to answer them -- that's bad form. And
>>> kinda pitiful.
>>>
>>>
>> I am really not that sad. Just spent quite some time hunting for any
>> help on the net, then stumbled across this site.
>
> I know how it goes. Sometimes it seems that you just have to expose your
> ignorance in public, then POOF! the answer drops into your lap.
>
Well I'm now having problems in changing peripheral registers, or their
memory locations in "memory monitor".
I make a change and as soon as I hit return the value springs back to
its reset value. Similarly for peripheral register values which
similarly spring back after a step instruction!
Reply by Tim Wescott●February 20, 20132013-02-20
On Wed, 20 Feb 2013 03:16:16 +0000, Fredxx wrote:
> On 20/02/2013 02:07, Tim Wescott wrote:
>> On Tue, 19 Feb 2013 22:52:37 +0000, Fredxx wrote:
>>
>>> On 19/02/2013 22:30, Fredxx wrote:
>>>> I can get the build and basic debug working, but wondering if there
>>>> was any easy way of viewing or manually changing CPU internal
>>>> registers, such as SPI and GPIO?
>>>>
>>>> I'm currently stumped and wondering if this is actually achievable?
>>>
>>> It may be bad form to reply to your own question, but the answer is
>>> here: http://embsysregview.sourceforge.net/
>>
>> I think it's just fine -- someone raised a question, someone answered
>> it.
>>
>> If you go asking questions just to answer them -- that's bad form. And
>> kinda pitiful.
>>
>>
> I am really not that sad. Just spent quite some time hunting for any
> help on the net, then stumbled across this site.
I know how it goes. Sometimes it seems that you just have to expose your
ignorance in public, then POOF! the answer drops into your lap.
--
Tim Wescott
Control system and signal processing consulting
www.wescottdesign.com