Hi Alan,
Thank you for your quick response.
I've tried the command nrf5 mass_erase:
(gdb) monitor nrf5 mass_erase
Flash protection of this nRF device is not supported
Failed to check chip's write protection
But without success.
What am I doing wrong here?
> -----------------------------------------------------------
>
> On 3/15/20, acas...@gmail.com wrote:
>
> Hi Kristof,
> you are using the command to nrf51, but your nrf52.
> As you could see in the second command I sent you, you should use:
> nrf5 mass_erase
>
> BR,
> Alan
>
> -----------------------------------------------------------
>
> On 3/15/20, kristof.mul...@telenet.be <kristof.mul...@telenet.be> wrote:
> Dear Mr. Alan Carvalho de Assis
> and
> Mr. Tomas Vanek,
>
> Thank you very much for your quick reply. I've tried the
> command to mass erase the chip. From GDB:
>
> (gdb) monitor nrf51 mass_erase
> Flash protection of this nRF device is not supported
> Failed to check chip's write protection
>
> Unfortunately, this doesn't work. OpenOCD seems to be
> unable to handle the chip's write protection. I'm using
> the following version:
>
> Open On-Chip Debugger 0.10.0+dev-00973-g80f1a92bd
> (2019-12-02-17:58)
>
> As you can see, I built this OpenOCD on December 2nd 2019
> for Windows 10.
> I've built it using the xPack method from Mr. Liviu Ionescu
> (see https://xpack.github.io/ and
> https://embeetle.com/#embedded-dev/software/dev-tools/flash/openocd_build )
>
>
> I've just built OpenOCD again today. Now I've got the following
> version:
>
> Open On-Chip Debugger 0.10.0+dev-01133-ge03de33c
> (2020-03-15-08:55)
>
> How can I be sure that merge 5348 (see http://openocd.zylin.com/#/c/5348/)
> is included in this build?
> Anyhow, it doesn't look good because I still get the same problem
> when trying a mass erase:
>
> (gdb) monitor nrf51 mass_erase
> Flash protection of this nRF device is not supported
> Failed to check chip's write protection
>
> Many thanks for your help ^_^
> Kind regards,
> Kristof Mulier
>
> -----------------------------------------------------------
>
> On 3/14/20 at 23:35, tom_...@users.sourceforge.net wrote:
>> The problem was solved by http://openocd.zylin.com/5348
>> Please use a newer OpenOCD build.
>> Tomas
>
> -----------------------------------------------------------
>
> On 3/14/20 at 23:40, acas...@gmail.com wrote:
>> Hi Kristof,
>> I just you missed the mass erase command to fix it, I faced same issue
>> with nRF51 some years ago:
>> https://acassis.wordpress.com/2015/10/21/nrf51822-and-openocd-cannot-erase-protected-sector-at-0x0/
>>
>>
>> I think nRF52833 is just same nRF52833 but for industrial grade. I
>> also used OpenOCD with nRF52:
>> https://acassis.wordpress.com/2018/04/03/how-to-install-nuttx-on-nordic-nrf52832/
>>
>>
>> BR,
>> Alan
>
> -----------------------------------------------------------
>
> On 3/14/20 at 22:57, kristof.mul...@telenet.be wrote:
>> Hi everyone,
>> I'm one of the cofounders of Embeetle IDE - a new free microcontroller
>> IDE.
>> We're using OpenOCD to flash the microcontrollers. So first I'd like to
>> express my gratitude to all of you for this free software.
>>
>> Currently, I'm trying to support a set of microcontrollers from Nordic
>> Semiconductor . I start with the nRF52833 microcontroller (on the PC10100
>>
>> development board). Unfortunately, OpenOCD has a problem with the flash
>> protection of this device. Everything is explained in my post on the
>> Nordic
>> DevZone:
>>
>> https://devzone.nordicsemi.com/f/nordic-q-a/59106/i-m-trying-to-support-nrf52833-in-embeetle-ide-but-flashing-through-openocd-gdb-doesn-t-work
>>
>>
>> Your help is greatly appreciated.
>> Kind regards,
>> Kristof Mulier
>
>
>
_______________________________________________
OpenOCD-devel mailing list
OpenOCD-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openocd-devel
