Hello Gary :-)
On Tue, Aug 23, 2011 at 2:24 AM, Gary Carlson
wrote:
> I have zero prior experience with the FT2232 so I took a very brief scan of
> its driver code. I get the feeling that this type of device allows fairly
> low-level access to interface port pins. If this is true I can see the
Why change the target scripts?
Perhaps a config option like:
openocd -c "rtos auto"
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/
___
Openocd-develo
I'll trust you on this one.
Any objections?
--
Øyvind Harboe - Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/
___
Openocd-development mailing list
Openocd-development@lists.b
Hi All,
Attached are two patches that fix bugs that I've found in FreeRTOS thread
awareness.
Regards,
Evan Hunter
Broadcom
0001-Fix-FreeRTOS-thread-list-parsing.patch
Description: 0001-Fix-FreeRTOS-thread-list-parsing.patch
0002-Add-suspended-task-list-to-FreeRTOS-support.patch
Description
Hi All,
I would like propose that the TCL scripts for Cortex-M3 systems be updated to
turn on automatic RTOS detection.
What does everyone think? The effects should be benign if no known RTOS is
detected...
It would simply involve adding "-rtos auto" to the end of the target configure
comm
Hi Tomek,
I have zero prior experience with the FT2232 so I took a very brief scan of
its driver code. I get the feeling that this type of device allows fairly
low-level access to interface port pins. If this is true I can see the
logic behind a bitbang function as this provides the generic abst
On 19:35 Tue 09 Aug , Jean-Christophe PLAGNIOL-VILLARD wrote:
> tested in buildroot
any comments?
Best Regards,
J.
>
> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD
> ---
> configure.in |7 +--
> 1 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/configure.in b/con
Currently the board/redbee-*.cfg files incorrectly include the
interface definition. Move the interfaces to interface/,
and create a single board/redbee.cfg that is common to both boards.
Intended usage is now:
openocd -f interface/redbee-econotag.cfg -f board/redbee.cfg
---
Øyvind Harboe wrote
On Mon, Aug 22, 2011 at 9:25 PM, Jim Paris wrote:
> The interface needs to be defined first, otherwise
> 'openocd -f board/redbee-econotag.cfg' gives an error.
This is supposed to fail. You need to split interface and board to
do something like:
openocd -f interface/foo.cfg -f board/redbee-econo
The interface needs to be defined first, otherwise
'openocd -f board/redbee-econotag.cfg' gives an error.
At the same time, clean things up by moving the interface
definitions into interface/
---
> In general the interface definition should be removed from the board
> file entirely.
How about thi
10 matches
Mail list logo