Hi Guys,
Here is the debug (-d) outputs using v0.8-dev:
Before launching GDB :
https://www.dropbox.com/sh/orb5lmxkkwam6x2/uoS6qXP04J/OpenOCD_before_GDB.txt
After Launching GDB:
https://www.dropbox.com/sh/orb5lmxkkwam6x2/wBYgzQRhKh/OpenOCD_after_GDB.txt
Note: the log might be missing some lines (from the beginning), because
this is executed and captured in a DOS window.
Cheers./
On Sat, Oct 5, 2013 at 11:48 AM, Nader <nsheha...@gmail.com> wrote:
> Hi Andreas,
>
> Here are my findings. Thanks for the quick link.
>
> As a sanity check, the same application with <1MB of flash size, still
> works OK and all is happy, with the new 0.8.0-dev-00094-gc658229.
>
> First thing you notice that the flash info reports a way much better
> sectors layout, with the correct size of 0x00200000 (2048kbytes).
>
>
> With the same application but >1MB, there is improvement but still not
> loading properly with new errors. see below.
>
> Notes:
> - The MCU is not protected, i can reload the smaller app after these
> errors and it will work OK again.
> - The improvement is, it is trying to erase this time, compared to the
> older v 0.7 .
> - GDB error showing still: Error erasing flash with vFlashErase packet
> - still using the 2 default config files (that comes with v0.8-dev):
> target->stm32f4x_stlink.cfg and interface->stlink-v2.cfg
> - I tried increase the work size to 0x20000 from 0x10000, stills same
> error.
>
> Cheers,
>
>
> **************** OpenOCD Output with the error >1MB flash v0.8 *******
> text data bss dec hex
> 1163612 4568 185896 1354076 14a95c
> *********************************************************************************
>
> Open On-Chip Debugger 0.8.0-dev-00094-gc658229 (2013-07-21-11:22)
>
> Licensed under GNU GPL v2
> For bug reports, read
> http://openocd.sourceforge.net/doc/doxygen/bugs.html
> trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
> connect_deassert_srst
> Info : This adapter doesn't support configurable speed
> Info : STLINK v2 JTAG v17 API v2 SWIM v0 VID 0x0483 PID 0x3748
> Info : Target voltage: 2.877745
>
> Info : stm32f4x.cpu: hardware has 6 breakpoints, 4 watchpoints
> Info : accepting 'gdb' connection from 3333
> Info : device id = 0x10036419
> Info : flash size = 2048kbytes
> Warn : acknowledgment received, but no packet pending
> undefined debug reason 6 - target needs reset
> target state: halted
> target halted due to debug-request, current mode: Thread
> xPSR: 0x01000000 pc: 0xfffffffe msp: 0xfffffffc
>
> Info : device id = 0x10036419
> Info : flash size = 2048kbytes
> flash 'stm32f2x' found at 0x08000000
> #0 : stm32f2x at 0x08000000, size 0x00200000, buswidth 0, chipwidth 0
>
> # 0: 0x00000000 (0x4000 16kB) not protected
> # 1: 0x00004000 (0x4000 16kB) not protected
> # 2: 0x00008000 (0x4000 16kB) not protected
> # 3: 0x0000c000 (0x4000 16kB) not protected
> # 4: 0x00010000 (0x10000 64kB) not protected
> # 5: 0x00020000 (0x20000 128kB) not protected
> # 6: 0x00040000 (0x20000 128kB) not protected
> # 7: 0x00060000 (0x20000 128kB) not protected
> # 8: 0x00080000 (0x20000 128kB) not protected
> # 9: 0x000a0000 (0x20000 128kB) not protected
> # 10: 0x000c0000 (0x20000 128kB) not protected
> # 11: 0x000e0000 (0x20000 128kB) not protected
> # 12: 0x00100000 (0x4000 16kB) not protected
> # 13: 0x00104000 (0x4000 16kB) not protected
> # 14: 0x00108000 (0x4000 16kB) not protected
> # 15: 0x0010c000 (0x4000 16kB) not protected
> # 16: 0x00110000 (0x10000 64kB) not protected
> # 17: 0x00120000 (0x20000 128kB) not protected
> # 18: 0x00140000 (0x20000 128kB) not protected
> # 19: 0x00160000 (0x20000 128kB) not protected
> # 20: 0x00180000 (0x20000 128kB) not protected
> # 21: 0x001a0000 (0x20000 128kB) not protected
> # 22: 0x001c0000 (0x20000 128kB) not protected
> # 23: 0x001e0000 (0x20000 128kB) not protected
> STM32F4xx - Rev: unknown (0x1003)
>
> requesting target halt and executing a soft reset
> Error: stm32x device protected
> Error: failed erasing sectors 0 to 16
> Error: flash_erase returned -4
>
> ******************************************************************************
>
>
>
>
>
>
>
>
>
> On Sat, Oct 5, 2013 at 10:53 AM, Andreas Fritiofson <
> andreas.fritiof...@gmail.com> wrote:
>
>>
>> On Sat, Oct 5, 2013 at 6:28 PM, Nader <nsheha...@gmail.com> wrote:
>>
>>> Hi Paul, Andres and All,
>>>
>>> Thanks for your prompt reply, first I will check with Freddie if he
>>> has any beta release for windows, second i will try to compile my own. I
>>> was able to compile my own before (it took lots of effort - specially the
>>> supporting libraries and requirements needed for the build-because i am
>>> purely on windows, so I decided to keep it for the pros :) , I will try
>>> again ASAP, and let you know.
>>>
>>>
>> http://www.freddiechopin.info/en/download/category/10-openocd-dev?download=101%3Aopenocd-0.8.0-dev-130717143429
>>
>> In case you haven't found it yet.
>>
>> In the mean time if you guys had any more ideas, please let me know.
>>>
>>
>> I'm pretty sure it'll work with a later version.
>>
>> /Andreas
>>
>
>
>
> --
> Nader Shehayed
>
>
>
--
Nader Shehayed
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
