On Sat, Jul 11, 2009 at 5:18 PM, Peter Denison wrote:
> On Sat, 11 Jul 2009, Øyvind Harboe wrote:
>
>> There is one more thing that is unclear from what you have
>> reported.
>>
>> Is this a problem with XScale or USBprog?
>
> It's definitely a problem with USBprog.
>
>> What if your assumption fal
On Sat, 11 Jul 2009, Øyvind Harboe wrote:
There is one more thing that is unclear from what you have
reported.
Is this a problem with XScale or USBprog?
It's definitely a problem with USBprog.
What if your assumption false: USBprog could be working
just fine w/short sequences today
Gi
There is one more thing that is unclear from what you have
reported.
Is this a problem with XScale or USBprog?
What if your assumption false: USBprog could be working
just fine w/short sequences today
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
_
On Sat, 11 Jul 2009, Øyvind Harboe wrote:
On Sat, Jul 11, 2009 at 10:24 AM, Peter Denison wrote:
On Sat, 11 Jul 2009, Øyvind Harboe wrote:
If I could return to the original point of this thread - getting the USBprog
adapter to work at all - in the light of the other comments, are you going
to
On Sat, Jul 11, 2009 at 10:24 AM, Peter Denison wrote:
> On Sat, 11 Jul 2009, Øyvind Harboe wrote:
>
>> We need to move on with development and j-link is still being
>> discussed actively. 0.2 is likely to be cut in the next 24-48 hours.
>>
>> We'll be releasing 0.3 soon after 0.2 anyway(a month or
On Sat, Jul 11, 2009 at 4:24 PM, Peter Denison wrote:
> On Sat, 11 Jul 2009, Øyvind Harboe wrote:
>
>> We need to move on with development and j-link is still being
>> discussed actively. 0.2 is likely to be cut in the next 24-48 hours.
>>
>> We'll be releasing 0.3 soon after 0.2 anyway(a month or
On Sat, 11 Jul 2009, Øyvind Harboe wrote:
We need to move on with development and j-link is still being
discussed actively. 0.2 is likely to be cut in the next 24-48 hours.
We'll be releasing 0.3 soon after 0.2 anyway(a month or two), so
this shouldn't be so bad. There are a handful of other pr
On Sat, Jul 11, 2009 at 1:34 AM, Xiaofan Chen wrote:
> 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
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 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
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
I've recently had the opportunity to start testing the USBprog interface
again.
Since the introduction of the "short" tms transition table, the USBprog
interface has been broken. The attached patch fixes it in one way, but I
don't really like the fact that it can be undone from the command prom
15 matches
Mail list logo
