-------- Mensaje reenviado --------
Asunto: Re: [OpenOCD-devel] [openocd:tickets] #117 PIC32MX bulk write algorithm failure
Fecha:  Sun, 31 Jan 2016 10:06:01 +0100
De:     Salvador <[email protected]>
Para:   Ticket 117 <[email protected]>



The code you are looking for is in file mips_mk4.c in function mips_m4k_bulk_write_memory():
......................................
if (address <= fast_data_area->address + fast_data_area->size &&
            fast_data_area->address <= address + count) {
.....................................
The purpose of the code is to warn the user, it's going to overwrite the handler memory.

A simple way to reproduce the fail (with default settings in pic32mx.cfg):
.........................................
> mww 0xa0000880 0 0x21
fast_data (0xa0000800) is within write area (0xa0000880-0xa00008a1).
Change work-area-phys or load_image address!
Falling back to non-bulk write
.........................................

Fast data handler starts at 0xa0000800. The length is 0x80 (MIPS32_FASTDATA_HANDLER_SIZE).
The end address is 0xa000087c.
Obviously outside write area.

Problems:
-Better comment
-Recheck limits, perhaps "<" instead of "<=" solves the problem.
-The final write address is wrong, at least should be multiple of 4.

Feel free to send a patch.





El 29/01/16 a las 22:20, ethereal escribió:
------------------------------------------------------------------------

*[tickets:#117] <http://sourceforge.net/p/openocd/tickets/117/> PIC32MX bulk write algorithm failure*

*Status:* new
*Milestone:* 0.9.0
*Created:* Fri Jan 29, 2016 09:20 PM UTC by ethereal
*Last Updated:* Fri Jan 29, 2016 09:20 PM UTC
*Owner:* nobody

Hi,

When programming a PIC32MX250F128B, the bulk write algorithm fails with the following message:

Error: fast_data (0xa00008d8) is within write area (0xa0000958-0xa0001158).

This is consistent across different HEX files. I'll be looking over the source code for the next little while myself, but I don't have much hope of it being useful. If someone with more familiarity with the PIC32MX code could take a look, it would be much appreciated.

Let me know what other information would be useful, and I'll try to provide.

Thanks!

  * ethereal

------------------------------------------------------------------------

Sent from sourceforge.net because [email protected] is subscribed to https://sourceforge.net/p/openocd/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140


_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel



------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel

Reply via email to