Re: [Openocd-development] Nasty problem with target_write_memory()

2010-02-09 Thread Øyvind Harboe
Ouch it's actually target_write_buffer() that breaks these rules target_write_buffer() aligns only the target address and does not consider the host address... As the jtag_add_xxscan() API is byte based, then we manage to escape problems, but post 0.4 I think target_write_buffer() should

Re: [Openocd-development] Nasty problem with target_write_memory()

2010-02-09 Thread David Brownell
On Tuesday 09 February 2010, Øyvind Harboe wrote: > The prototype below is problematic I would like to have > seen buffer defined as "const void *" and added the requirement > that "buffer" should be aligned to match "size" > > int target_write_memory(struct target *target, >

[Openocd-development] Nasty problem with target_write_memory()

2010-02-09 Thread Øyvind Harboe
The prototype below is problematic I would like to have seen buffer defined as "const void *" and added the requirement that "buffer" should be aligned to match "size" int target_write_memory(struct target *target, uint32_t address, uint32_t size, uint32_t count, uint8_t *