On Mon, Dec 6, 2010 at 5:43 PM, Nick Pelling wrote:
> (...) constructing a suitable target cfg file for it. I've asked Samsung for
> documentation listing all its JTAG codes,
Btw. have you tried UrJTAG and the "discovery" command - it helps
finding such registers on unknown devices :-)
--
CeDeR
On Mon, Dec 6, 2010 at 5:43 PM, Nick Pelling wrote:
> (...)constructing a suitable target cfg file for it. I've asked Samsung for
> documentation listing all its JTAG codes, but that may take some time to
Hello Nick, the other problem is that Samsung may want you to sign the
NDA and keep quiet ab
Merged.
I built it under Linux Ubuntu 10, had to fix some more size_t
warnings.
--
Ø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 progr
On Sun, Dec 5, 2010 at 11:19 PM, Øyvind Harboe wrote:
>> I'm happy with the previous set of patches I submitted (nov 30),
>> it's been working well for me for the past couple of weeks
>> with no issues.
>
> I had to make some fixes to make it compile.
>
> Could you read over the patch now and writ
If the JTAG speed has not been set, then it has no defined
value, add code to propagate the error.
Signed-off-by: Øyvind Harboe
---
src/jtag/core.c | 27 +--
src/jtag/drivers/amt_jtagaccel.c | 19 ---
src/jtag/drivers/ft2232.c|
--- On Mon, 12/6/10, Karl Kurbjun wrote:
> All device vendors should provide BSDL files for their devices
Yes, and they're not necessarily easy to find.
which
> specify the maximum TCK speed the device can support.
On appropriately designed and manufactured
boards, only. So that's an
On Mon, Dec 6, 2010 at 12:33 PM, Øyvind Harboe wrote:
> I believe that there might exist a safe default or autodetection
> scheme for a specific family of parts.
>
> Such parts could use a common configuration file which
> did the autodetect/set the robust default frequency.
>
> The responsibility
I believe that there might exist a safe default or autodetection
scheme for a specific family of parts.
Such parts could use a common configuration file which
did the autodetect/set the robust default frequency.
The responsibility for deciding how to deal with JTAG clk
is still firmly in the boar
Hi.
I'm interesting in reading and then reflashing OMAP35x NAND on a beagleboard
rev
C3.
Can somebody help me with is the correct procedure? I am a little warry of
ruining the board, and the search I did on the web so far was less than
conclusive on the matter.
Is it something similarly simp
On 12/06/2010 10:53 AM, Laurent Gauch wrote:
>
>
> Øyvind Harboe wrote:
>> I don't subscribe to the idea that there is a safe, correct and robust
>> default setting for JTAG clock, better to make the user get a
>> good error message that points him in the right direction.
>>
>> 1MHz will fail on pl
--- On Mon, 12/6/10, Laurent Gauch wrote:
> > I don't subscribe to the idea that there is a safe,
> correct and robust
> > default setting for JTAG clock,
The only thing that'd prevent a given board from
having such a (board-specific) setting is using
it with a debug adapter that doesn't su
Hi everyone,
Using the Bus Pirate's JTAG macros, my S5PC100 returns a valid 3.3V
JTAG chain with 250 devices (it's a highly integrated SoC, so 250
sounds like a plausible number), each with IDCODE = 0: while a
Cortex-M3 microcontroller returns a single-device chain with the
correct id value.
Hello,
I got an ATSAM3U4E-ek board, openocd can read out chip very well, but
when flashing the internal bank it has very low speed:
wrote 54652 bytes from file
bin/usb-device-massstorage-project-at91sam3u-ek-at91sam3u4-flash.bin
in 84.920578s (0.628 kb/s)
is this the driver in openocd's problem
Hi Spen,
Spencer Oliver wrote:
> On 23/11/2010 03:04, Antonio Borneo wrote:
>> Jonathan,
>> could you please report the full part number of the flash chip?
>> Form the log, seems Numonyx M29W128G
>>Flash Manufacturer/Device: 0x0020 0x227e
>>
>> Spencer,
>> the flash M29W128G has a HW bug. Num
It has already been mentioned on the list that it is obviously
correct for OpenOCD to have and use knowledge about components,
in order to determine useful values for various parameters. I don't
think that needs to be said again. But please do help with the steps
that are required to get there.
Laurent Gauch wrote:
> THE SAFE CORRECT ROBUST frequency can never be known as static !
> A good JTAG software has to find this frequency by itself
Which is an important usability enhancement that can only be done
sensibly *AFTER* there is a proper and enforced way to set the speed.
I am sure you
For something like OpenOCD where anything could be connected,
you will easily end up in a situation that 1MHz kinda works, which is
the worst possible situation.
Better to tell the user that a configuration script must have made a
decision on how to deal with JTAG clock frequency. That decision
co
Øyvind Harboe wrote:
I don't subscribe to the idea that there is a safe, correct and robust
default setting for JTAG clock, better to make the user get a
good error message that points him in the right direction.
1MHz will fail on plenty of cards (with RC oscilators typically).
I do not sa
David Brownell wrote:
> > Basically, I'd like OpenOCD to refuse to start until the script
> > defines the clock rate.
>
> Script is the right place, yes. Not *ANY* of
> the adapter drivers, or embedded in OpenOCD
> framework code either.
I like this. And specifically I think that trying to set s
I don't subscribe to the idea that there is a safe, correct and robust
default setting for JTAG clock, better to make the user get a
good error message that points him in the right direction.
1MHz will fail on plenty of cards (with RC oscilators typically).
--
Øyvind Harboe
Can Zylin Consulting
Does anyone have any objections to getting rid of the
concept of a default JTAG clock rate?
Basically, I'd like OpenOCD to refuse to start until the
script defines the clock rate.
The actual mechanism needs a bit of though, because it
is possible to set jtag clock rate in reset-start and in my
b
A starting patch, propagate error for getting speed.
In the future it will fail when no jtag speed has been set
before someone queries the speed.
--
Ø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
22 matches
Mail list logo
