On 2010-12-05 14:46, Øyvind Harboe wrote:
Try with the currently committed stuff:
openocd -c "set CCLK 12345; source [find target/lpc2478.cfg]"
Well, it works, but I can't say that it's convenient to run OpenOCD this
way, when one "global CCLK" makes it easier. I prefer to do it "the
normal
Try with the currently committed stuff:
openocd -c "set CCLK 12345; source [find target/lpc2478.cfg]"
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG deb
OK, now I have something that will probably reunite us all.
This patch allows OpenOCD to be run with this target script but define
CCLK via command line:
openocd -c "set CCLK 12345" -f target/lpc2478.cfg
It has only one downside, as I've noticed that OpenOCD prints the
value... The more funn
Merged.
I like the concept of mandatory instead of default values for
target scripts. A default value that works everywhere is great,
but it doesn't exist for this LPC chip.
I've actually been thinking about modifying OpenOCD to complain
if a board + target script does not define a JTAG clock fre
Oh - another solution is creating a board file that defines all that is
necessary. Such board file could also define some default values of
reset_config, adapter_khz etc. I'm starting to like that idea (; The
only problem is the amount of new files that would be created this way...
4\/3!!
On 2010-12-05 10:13, Andrew Leech wrote:
On 05/12/2010, at 7:49 PM, Freddie Chopin wrote:
On 2010-12-04 19:29, Michael Schwingen wrote:
Just because the current files are hard-wired in a way that suits you
does not mean they work fine for everyone.
Have you considered opposite approach? Just
On 05/12/2010, at 7:49 PM, Freddie Chopin wrote:
> On 2010-12-04 19:29, Michael Schwingen wrote:
>> Just because the current files are hard-wired in a way that suits you
>> does not mean they work fine for everyone.
>
> Have you considered opposite approach? Just because the need of creating
>
On 2010-12-04 19:29, Michael Schwingen wrote:
Just because the current files are hard-wired in a way that suits you
does not mean they work fine for everyone.
Have you considered opposite approach? Just because the need of creating
another file suits you does not mean this is fine for everyone
On 04.12.2010 10:08, Freddie Chopin wrote:
So you're all about correctness and you don't reset halt the chip before
flashing? How is that correct? Actually flashing does not work if you
don't "reset halt" the chip. The need for halting is obvious. The need
for reset is not, but think about what w
On 04.12.2010 10:31, Freddie Chopin wrote:
As for the second paragraph, you are wrong. All LPC2xxx target config
files have that frequency embedded without possibility to change with
some parameters in board config files and - somehow - people manage to
use it without problems.
How do you know?
Here is my vision of this patch - with default value.
4\/3!!
From f573665d0ea4afbacff730c2591cf593374097b7 Mon Sep 17 00:00:00 2001
From: Rolf Meeser
Date: Fri, 3 Dec 2010 14:10:40 +0100
Subject: [PATCH] lpc2478 target config: CCLK as (optional) parameter
Differences to original patch: CCLK is
On 2010-12-04 13:59, Rolf Meeser wrote:
Definitely my last post on this thread.
On 12/04/2010 12:33 PM, Freddie Chopin wrote:
On 2010-12-04 12:05, Rolf Meeser wrote:
When doing "reset halt" (which would halt the chip immediately after
reset) the clock would be 4MHz.
Wrong. I've explained tha
On 2010-12-04 13:59, Rolf Meeser wrote:
Definitely my last post on this thread.
If that's the case then there's no need to reply...
4\/3!!
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/list
Definitely my last post on this thread.
On 12/04/2010 12:33 PM, Freddie Chopin wrote:
On 2010-12-04 12:05, Rolf Meeser wrote:
When doing "reset halt" (which would halt the chip immediately after
reset) the clock would be 4MHz.
Wrong. I've explained that often enough.
So you say that after r
On 4.12.2010 13:35, Freddie Chopin wrote:
Speaking about this right/wrong policy - it's said that reset_config
does not belong to target config files, yet you haven't changed that,
but left these "wrong" command there... How come?
Funny thing, each time I recall a discussion about LPC2xxx scr
On 12/04/2010 12:35 PM, Freddie Chopin wrote:
On 2010-12-04 12:05, Rolf Meeser wrote:
For me this policy is right. I'm willing to state this on as many
occasions as required.
Speaking about this right/wrong policy - it's said that reset_config
does not belong to target config files, yet you h
On 2010-12-04 12:05, Rolf Meeser wrote:
For me this policy is right. I'm willing to state this on as many
occasions as required.
Speaking about this right/wrong policy - it's said that reset_config
does not belong to target config files, yet you haven't changed that,
but left these "wrong" co
On 2010-12-04 12:05, Rolf Meeser wrote:
When doing "reset halt" (which would halt the chip immediately after
reset) the clock would be 4MHz.
Wrong. I've explained that often enough.
So you say that after reset and immediate halt the chip clock (for new
LPCs) is not 4MHz? Are you working for
On 12/04/2010 10:31 AM, Freddie Chopin wrote:
On 2010-12-04 00:32, Rolf Meeser wrote:
This is a misconception. When OpenOCD tries to take control after a
reset, the CPU is already running. ISP mode or existing user firmware
may or may not have changed the clock tree. Like it or not, but there is
On 2010-12-04 00:32, Rolf Meeser wrote:
This is a misconception. When OpenOCD tries to take control after a
reset, the CPU is already running. ISP mode or existing user firmware
may or may not have changed the clock tree. Like it or not, but there is
no a priori knowledge of CPU clock.
When doi
On 2010-12-04 00:00, Michael Schwingen wrote:
On 12/03/2010 11:11 PM, Freddie Chopin wrote:
How can this be unreliable? LPC23xx/LPC24xx after reset use 4MHz
internal clock. Doing "reset halt" sets that clock and prevents any
code from changing that (let's not talk about broken cases, because a
b
Hi Freddie,
On 12/03/2010 11:11 PM, Freddie Chopin wrote:
How can this be unreliable? LPC23xx/LPC24xx after reset use 4MHz
internal clock. Doing "reset halt" sets that clock and prevents any
code from changing that (let's not talk about broken cases, because a
broken case can be found everywhe
On 12/03/2010 11:11 PM, Freddie Chopin wrote:
> How can this be unreliable? LPC23xx/LPC24xx after reset use 4MHz
> internal clock. Doing "reset halt" sets that clock and prevents any
> code from changing that (let's not talk about broken cases, because a
> broken case can be found everywhere), so w
On 2010-12-03 22:42, Michael Schwingen wrote:
On 12/03/2010 10:06 PM, Freddie Chopin wrote:
On 2010-12-03 21:39, Rolf Meeser wrote:
The clock parameter is vital for correct and reliable flash programming.
It must be possible for the user to select the frequency that he is
using.
I don't know h
On 12/03/2010 10:06 PM, Freddie Chopin wrote:
> On 2010-12-03 21:39, Rolf Meeser wrote:
>> The clock parameter is vital for correct and reliable flash programming.
>> It must be possible for the user to select the frequency that he is
>> using.
> I don't know how about you, but me (and 99% of "norm
On 12/03/2010 10:12 PM, Freddie Chopin wrote:
>
> Crazy idea nr 2 - why not set max frequency - this way this pulse will
> always be long enough (I don't see any reason for problems with longer
> pulse) - maybe this way this parameter would not be required too?
I don't know about the flash in the L
On 2010-12-03 21:39, Rolf Meeser wrote:
If for instance the flash is empty, the device will enter ISP mode
automatically. It will activate the PLL, and from then on run with
14.748 MHz. When in this situation you program the flash with the clock
parameter set to 4 MHz, the programming pulse will
On 2010-12-03 21:39, Rolf Meeser wrote:
On 12/03/2010 08:09 PM, Freddie Chopin wrote:
First of all, the chip frequency after reset actually is 4MHz due to
internal RC oscillator, so this "default frequency" assumption seems
pretty correct (actually it was probably me who added that script to
Ope
Hi Freddie,
On 12/03/2010 08:09 PM, Freddie Chopin wrote:
First of all, the chip frequency after reset actually is 4MHz due to
internal RC oscillator, so this "default frequency" assumption seems
pretty correct (actually it was probably me who added that script to
OpenOCD).
Incorrect. Yes, the
On 2010-12-03 14:31, Rolf Meeser wrote:
This patch allows a board script to specify the CPU clock of the LPC2478 target.
The clock frequency used to be fixed to 4 MHz. However, there is no default
frequency for this CPU. You mustn't assume prior knowledge of the clock
frequency, but rather dem
Looks good to me.
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-
Hi,
This patch allows a board script to specify the CPU clock of the LPC2478 target.
The clock frequency used to be fixed to 4 MHz. However, there is no default
frequency for this CPU. You mustn't assume prior knowledge of the clock
frequency, but rather demand that the user (board script) spec
32 matches
Mail list logo
