David Brownell escreveu:
> On Friday 12 June 2009, Alain Mouette wrote:
>> And on the wiki there are samples, but not for
>> Luminary-Cortex-M3
> You mean "Texas Instruments" yes? :)
yes.. but I am not sure it it is :) or :(
> In svn:
> tcl/interface/luminary*
> tcl/target/lm3s*cfg
> They
Here is a patch to the README file to document my experiment
with MinGW cross build.
Please feel free to change it if you think it needs some modifications.
Tips For Building From The Subversion Repository
Building OpenOCD from a repository requir
On Sat, Jul 11, 2009 at 7:07 AM, Xiaofan Chen wrote:
> On Sat, Jul 11, 2009 at 2:31 AM, Spencer Oliver wrote:
>>>
>>> A minor fix needs to be done as I mentioned before.
>>> usb_init(); needs to be moved up to the helper function
>>> find_jlink_device(void) (before the line usb_find_busses();)
>>>
Dominic has the following test results to show that libftdi is as good as
ftd2xx in Linux.
https://lists.berlios.de/pipermail/openocd-development/2009-June/008846.html
Freddie Choppin has the following results to show that libftdi is quite a bit
slower than ftd2xx under Windows.
https://lists.berl
2009/6/29 Øyvind Harboe :
> On Sun, Jun 28, 2009 at 11:13 PM, Michael Fischer
> wrote:
>>>Michael Fischer has maintained a really neat website with lots of
>>>Windows binaries. Why should we dilute his efforts?
>>
>> You can distribute Windows binaries on berlios. I will link
>> to it if available
On Sat, Jul 11, 2009 at 8:33 AM, Xiaofan Chen wrote:
> I was using similar udev rules for some USB device (mostly PIC
> related) as the udev contrib directory.
>
> udev seems to be a changing target in Linux. Many support
> questions raided in libusb mailing list and pickit-devel mailing
> list are
To All,
It turns out my big breakpoint problem was due to my using a makedefs file that
configured the gnu compiler to optimize for size. Apparently the
debugger needs to
have no optimizations on to work properly. Well I think I will rember
this solution for
a while !!.
# Debug and optimization f
I was using similar udev rules for some USB device (mostly PIC
related) as the udev contrib directory.
udev seems to be a changing target in Linux. Many support
questions raided in libusb mailing list and pickit-devel mailing
list are related in usb device permissions. For the PICkit 2
programmer,
I been doing a little more investigation as to why reset run, reset init,
and reset halt don¹t work with a jlink dongle and the Atmel AT91SAM9G20-EK
evaluation board. In the case of a simple reset command issued from the
telnet session this causes the following:
jtag_nsrst_delay: 200
jtag_ntrst_d
On Fri, Jul 10, 2009 at 9:50 PM, Øyvind Harboe wrote:
> I don't know if J-Link will work for 0.2. If nothing drastic happens
> in the 24 hours, it won't make it.
Please clarify this. What do you mean by J-link won't make it for 0.2?
It has already made a lot of progress and it one of the main feat
On Sat, Jul 11, 2009 at 2:31 AM, Spencer Oliver wrote:
>>
>> A minor fix needs to be done as I mentioned before.
>> usb_init(); needs to be moved up to the helper function
>> find_jlink_device(void) (before the line usb_find_busses();)
>> http://libusb.sourceforge.net/doc/examples-code.html
>>
>> C
>
> If they give a thumbs up, would you agree that committing the
> patch makes the most sense at this point given what we know
> today about libusb?
>
Looks good to me - only had time to test win32 however.
Cheers
Spen
___
Openocd-development mail
>
> A minor fix needs to be done as I mentioned before.
> usb_init(); needs to be moved up to the helper function
> find_jlink_device(void) (before the line usb_find_busses();)
> http://libusb.sourceforge.net/doc/examples-code.html
>
> Could you rework the patch? Thanks.
>
Why does it?
usb_in
In file target/str710.cfg got accidentally modified with a missing close
bracket on second line below:
:
$_TARGETNAME configure -event reset-start { jtag_khz 1000 }
$_TARGETNAME configure -event reset-init { jtag_khz 1000
$_TARGETNAME configure -event gdb-flash-erase-start {
flash protect 0
On Friday 10 July 2009, Peter Denison wrote:
> > The patch will not be applied before 0.2 as there is a workaround.
>
> What workaround? Expecting anyone that uses it to work out that they
> need an extra line in their config file? At least we should make this
> adapter default to the correct ta
On Fri, 10 Jul 2009, Øyvind Harboe wrote:
It's trivial in the sense that there's absolutely no way the adapter can
work with the short transition table,
Could you elaborate on this for those that read up on this thread later on?
The USBprog adapter expects 7-bit sequences to be sent as part
> It's trivial in the sense that there's absolutely no way the adapter can
> work with the short transition table,
Could you elaborate on this for those that read up on this thread later on?
> and some degree of getting it working with the original long one.
I've added an item in TODO for this p
On Fri, 10 Jul 2009, Øyvind Harboe wrote:
This is not a trivial regression and I believe the XScale
target code needs to be fixed.
It's trivial in the sense that there's absolutely no way the adapter can
work with the short transition table, and some degree of getting it
working with the ori
On 7/9/09 8:49 AM, "Alan Carvalho de Assis" wrote:
> Hi,
>
> On 7/9/09, Xiaofan Chen wrote:
>>
>> It would be nice to have a unified patch. But it seems a bit difficult here.
>> Maybe we can accept this as a temporary fix while investigating a better
>> fix.
>>
>
> Jlink still failing to
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
This is not a trivial regression and I believe the XScale
target code needs to be fixed.
What XScale target are you testing against?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mai
My definition of a developer is a person who, with minimal guidance, can:
- read and understand a short "hackers guide readme"
- check out svn head
- bootstrap it
- build it
- install it
- read and post to the developer mailing list, including
a minimum of skills in terms of what's expected and
wh
22 matches
Mail list logo
