[Openocd-development] Next release

2011-08-24 Thread Øyvind Harboe 
Hi,

is anyone out there working on something that they would like
to see in the next release?

I know Tomek has been working on SWD. Here we need resources
to review, give feedback and look into what it would take to bring
this to a state where the community is happy to take responsibility
for it.

Other things?



-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] Add STM32 value line MD and HD support

2011-08-24 Thread Jonathan Dumaresq 
Hi,

I have added the Value line HD support. Thsi have been tested in a real HD
chip. STM32T100VE

Jonathan Dumaresq


0002-Add-Valuline-HD-to-config-file.patch
Description: Binary data


0001-This-will-add-the-Value-Line-HD-of-stm32-devices.patch
Description: Binary data
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] Request for patch to enable RTOS support by default

2011-08-24 Thread Øyvind Harboe 
I'd like to see a patch that does the following:

- enable RTOS by default
- add documentation to openocd.texi on how to disable RTOS support, typically to
do early RTOS startup debugging and to explain a bit why it's pretty
safe to have
this enabled by default.

Once RTOS is enabled by default, I'm hopeful that ARM7/9 RTOS support patches
would follow

This would be a nice feature to have in the next version!

-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH] Remove target argument from gdb packet handling functions

2011-08-24 Thread Øyvind Harboe 
Merged.

Thanks!

-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH] Remove target argument from gdb packet handling functions

2011-08-24 Thread Jie Zhang 
On Wed, Aug 24, 2011 at 12:53 AM, Øyvind Harboe  wrote:
> I'm OK with this.
>
> Perhaps make a tiny static fn for:
>
> +       struct gdb_service *gdb_service = connection->service->priv;
> +       struct target *target = gdb_service->target;
>
I think this is a good idea. Ideally the function should be put in
gdb_server.c. But currently it needs to be in gdb_server.h. The new
patch is attached.

Regards,
Jie
From 8b73e67c7fcdfd0228d5cc2326bff47635daf84c Mon Sep 17 00:00:00 2001
From: Jie Zhang 
Date: Wed, 24 Aug 2011 11:23:04 -0400
Subject: [PATCH] remove target argument from gdb packet handling functions

---
 src/rtos/rtos.c |8 +++-
 src/rtos/rtos.h |4 +-
 src/server/gdb_server.c |  106 --
 src/server/gdb_server.h |6 +++
 src/target/smp.c|6 ++-
 src/target/smp.h|4 +-
 6 files changed, 66 insertions(+), 68 deletions(-)

diff --git a/src/rtos/rtos.c b/src/rtos/rtos.c
index 263795c..74e8724 100644
--- a/src/rtos/rtos.c
+++ b/src/rtos/rtos.c
@@ -128,8 +128,10 @@ int rtos_create(Jim_GetOptInfo *goi, struct target * target)
 
 
 
-int gdb_thread_packet(struct connection *connection, struct target *target, char *packet, int packet_size)
+int gdb_thread_packet(struct connection *connection, char *packet, int packet_size)
 {
+	struct target *target = get_target_from_connection(connection);
+
 	if (strstr(packet, "qP"))
 	{
 		#define TAG_THREADID 1		/* Echo the thread identifier */
@@ -501,8 +503,10 @@ int gdb_thread_packet(struct connection *connection, struct target *target, char
 	return GDB_THREAD_PACKET_NOT_CONSUMED;
 }
 
-int rtos_get_gdb_reg_list(struct connection *connection, struct target *target, struct reg **reg_list[], int *reg_list_size)
+int rtos_get_gdb_reg_list(struct connection *connection, struct reg **reg_list[], int *reg_list_size)
 {
+	struct target *target = get_target_from_connection(connection);
+
 	if ( ( target->rtos != NULL ) &&
 		 ( current_threadid != -1 ) &&
 		 ( current_threadid != 0 ) &&
diff --git a/src/rtos/rtos.h b/src/rtos/rtos.h
index a6378c6..1a73bd7 100644
--- a/src/rtos/rtos.h
+++ b/src/rtos/rtos.h
@@ -99,8 +99,8 @@ struct rtos_register_stacking
 int rtos_create(Jim_GetOptInfo *goi, struct target * target);
 int rtos_generic_stack_read( struct target * target, const struct rtos_register_stacking* stacking, int64_t stack_ptr, char ** hex_reg_list );
 int rtos_try_next( struct target * target );
-int gdb_thread_packet(struct connection *connection, struct target *target, char *packet, int packet_size);
-int rtos_get_gdb_reg_list(struct connection *connection, struct target *target, struct reg **reg_list[], int *reg_list_size);
+int gdb_thread_packet(struct connection *connection, char *packet, int packet_size);
+int rtos_get_gdb_reg_list(struct connection *connection, struct reg **reg_list[], int *reg_list_size);
 int rtos_update_threads( struct target *target );
 
 #endif // RTOS_H
diff --git a/src/server/gdb_server.c b/src/server/gdb_server.c
index b6921ff..5eb6cac 100644
--- a/src/server/gdb_server.c
+++ b/src/server/gdb_server.c
@@ -944,8 +944,9 @@ static void gdb_send_error(struct connection *connection, uint8_t the_error)
 }
 
 static int gdb_last_signal_packet(struct connection *connection,
-		struct target *target, char* packet, int packet_size)
+		char* packet, int packet_size)
 {
+	struct target *target = get_target_from_connection(connection);
 	char sig_reply[4];
 	int signal_var;
 
@@ -1029,8 +1030,9 @@ static void gdb_target_to_reg(struct target *target,
 }
 
 static int gdb_get_registers_packet(struct connection *connection,
-		struct target *target, char* packet, int packet_size)
+		char* packet, int packet_size)
 {
+	struct target *target = get_target_from_connection(connection);
 	struct reg **reg_list;
 	int reg_list_size;
 	int retval;
@@ -1044,7 +1046,7 @@ static int gdb_get_registers_packet(struct connection *connection,
 #endif
 
 	if ( ( target->rtos != NULL ) &&
-		 ( ERROR_FAIL != rtos_get_gdb_reg_list( connection, target, ®_list, ®_list_size) ) )
+		 ( ERROR_FAIL != rtos_get_gdb_reg_list( connection, ®_list, ®_list_size) ) )
 	{
 		return ERROR_OK;
 	}
@@ -1088,8 +1090,9 @@ static int gdb_get_registers_packet(struct connection *connection,
 }
 
 static int gdb_set_registers_packet(struct connection *connection,
-		struct target *target, char *packet, int packet_size)
+		char *packet, int packet_size)
 {
+	struct target *target = get_target_from_connection(connection);
 	int i;
 	struct reg **reg_list;
 	int reg_list_size;
@@ -1147,8 +1150,9 @@ static int gdb_set_registers_packet(struct connection *connection,
 }
 
 static int gdb_get_register_packet(struct connection *connection,
-		struct target *target, char *packet, int packet_size)
+		char *packet, int packet_size)
 {
+	struct target *target = get_target_from_connection(connection);
 	char *reg_packet;
 	int reg_num = strtoul(packet + 1, NULL, 16);
 	struct reg **reg_list;
@@ -1186,8 +1190,9 @@ sta

Re: [Openocd-development] Bugfix release (was: FreeRTOS bug fixes)

2011-08-24 Thread Simon Barner 
Dear Jean-Christophe,

On 24.08.2011 16:12, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 19:54 Tue 23 Aug , Øyvind Harboe wrote:
>> Do we need a bugfix release?
> yes I've a bug on the usb in cross comp when integrate openocd in buildroot
> 
> so I'll prepare a bugfix release within 1 or 2weeks
>>
>> When is the next release?
> I'm traveling right now so give me few days to prepare the next release plan
> 
>>
>> If someone needs a bugfix badly, then there is always git...
> no for distribution point of view we need bug fix release

I do not want to nag, but I would be very happy to see my fixes for the
ARM-JTAG-EW interfaces included in this bug fix release. This code has
been used successfully now for several weeks.

What would be the best way to submit them?

- The mailing list?
 -

 -


- The bug tracker? There are also tickets for the issues address be the
above patches, but the latest version of the patches are in the above
postings.

Thanks in advance,

Best regards,
 Simon
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] FreeRTOS bug fixes

2011-08-24 Thread Jean-Christophe PLAGNIOL-VILLARD 
On 19:54 Tue 23 Aug , Øyvind Harboe wrote:
> Do we need a bugfix release?
yes I've a bug on the usb in cross comp when integrate openocd in buildroot

so I'll prepare a bugfix release within 1 or 2weeks
> 
> When is the next release?
I'm traveling right now so give me few days to prepare the next release plan

> 
> If someone needs a bugfix badly, then there is always git...
no for distribution point of view we need bug fix release
> 
> -- 
> Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

[Openocd-development] [PATCH] Cortex_A context & hybrid breakpoints

2011-08-24 Thread Heythem BOUHAJA 
Hi

Cortex_A processors supports three kinds of hardware breakpoints

-IVA breakpoint which is currently implemented in OPENOCD
-Context ID breakpoint, based on the CONTEXTID register of the CP15 coprocessor 
, the breakpoint is hit when  the contextID specified with the bp command  is 
loaded into CP15 contextid register
-Context ID & IVA breakpoint (hybrid) which is a combination of the two other 
types of breakpoints(needs two BRPs linked together), the breakpoint is hit 
when the specified contextID is loaded into CP15 register and the PC reaches 
the specified IVA.

ContextID identifier is used by the cpu to differentiate between the processes 
running on the target so  the contextID breakpoint allows to stop the target 
when a given process is executing. The hybrid breakpoint allows to stop the 
target when a given process is executing and a given address within it's memory 
space is reached.

This patch adds the support for the ContextID and the Hybrid breakpoints

Add a contextID breakpoint:  bphw_ctx
Add a hybrid breakpoint:  bphw

Please review and merge if it's OK

Thanks


0002-cortex_a_bp.patch
Description: 0002-cortex_a_bp.patch


0003-cortex_a_bp.patch
Description: 0003-cortex_a_bp.patch
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] FreeRTOS bug fixes

2011-08-24 Thread Øyvind Harboe 
Merged.

Thanks!





-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH] non_cfi: add SST39WF1601 support

2011-08-24 Thread Øyvind Harboe 
Merged.

Thanks!
-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Re: [Openocd-development] [PATCH v3] Fix redbee config files

2011-08-24 Thread Øyvind Harboe 
Merged.

Thanks!




-- 
Ø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.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development