Re: [Openocd-development] [STM32] Error: failed erasing sectors after stm32x unlock 0

2011-02-03 Thread gcembed
On 02/03/2011 12:23 PM, Øyvind Harboe wrote: On Thu, Feb 3, 2011 at 12:16 PM, gcembed wrote: Hello, I have downloaded today last git repo of OpenOCD (git://repo.or.cz/openocd.git) As previously, I still have problem to erase and program STM32. I sent a patch to create unlock_mass_erase

[Openocd-development] [STM32] Error: failed erasing sectors after stm32x unlock 0

2011-02-03 Thread gcembed
Hello, I have downloaded today last git repo of OpenOCD (git://repo.or.cz/openocd.git) As previously, I still have problem to erase and program STM32. I sent a patch to create unlock_mass_erase function ([PATCH] stm32 : improve unlock procedure for mass_erase) but it was never accepted because

Re: [Openocd-development] invalid command name "jtag"

2010-08-31 Thread gcembed
Hello, I am very sorry to have disturbed you. It was my fault. With this version, I have to call jlink-segger.cfg before stm32.cfg. Everything is working now. Gaëtan On 08/31/2010 02:40 PM, gcembed wrote: Hello, I have just downloaded and compiled devel version of OpenOCD from Git repo (Open

[Openocd-development] invalid command name "jtag"

2010-08-31 Thread gcembed
Hello, I have just downloaded and compiled devel version of OpenOCD from Git repo (Open On-Chip Debugger 0.5.0-dev-00494-g5c98e06) and when I try to run OpenOCD with script files provided in tcl/target/, I have following error : (I comment jtag_ntrst_delay because it is also an invalid command

Re: [Openocd-development] [PATCH] stm32 : improve unlock procedure for mass_erase

2010-07-16 Thread gcembed
ks to see if anyone have a TCL solution, if not I will try to send a new patch for a new command. Best regards, Gaëtan On 07/16/2010 04:24 PM, Andreas Fritiofson wrote: On Fri, Jul 16, 2010 at 10:10 AM, gcembed wrote: Hello, I am back. Andreas, can I add something in stm32x_mass_erase()

Re: [Openocd-development] [PATCH] stm32 : improve unlock procedure for mass_erase

2010-07-16 Thread gcembed
, STM32_FLASH_KEYR, KEY2); Should I add a flag to mass_erase command to force or enable this feature. Does this check must be done automatically ? Thank you for your advise, Gaëtan On 06/01/2010 09:47 PM, Andreas Fritiofson wrote: On Tue, Jun 1, 2010 at 1:56 PM, gcembed wrote: Hello, I have added a

Re: [Openocd-development] [PATCH v2] stm32 : improve unlock procedure for mass_erase

2010-06-07 Thread gcembed
Hello, Sorry, I was working on an other project. I will try this this week. Thanks Gaëtan On 06/03/2010 06:08 PM, Øyvind Harboe wrote: try with "poll off"? ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.be

Re: [Openocd-development] [PATCH v2] stm32 : improve unlock procedure for mass_erase

2010-06-01 Thread gcembed
On 06/01/2010 10:03 PM, Øyvind Harboe wrote: On Tue, Jun 1, 2010 at 9:36 PM, Spencer Oliver wrote: On 01/06/2010 13:22, gcembed wrote: Here is the modified patch Gaëtan On 06/01/2010 02:01 PM, freddie_cho...@op.pl wrote: "gcembed" napisał(a): Hello, I have added a new command

Re: [Openocd-development] [PATCH v2] stm32 : improve unlock procedure for mass_erase

2010-06-01 Thread gcembed
Here is the modified patch Gaëtan On 06/01/2010 02:01 PM, freddie_cho...@op.pl wrote: "gcembed" napisał(a): > Hello, > I have added a new command for stm32x : mass_erase_unlock > This function combine "stm32x unlock 0" + reset to apply unlock + &g

[Openocd-development] [PATCH] stm32 : improve unlock procedure for mass_erase

2010-06-01 Thread gcembed
Hello, I have added a new command for stm32x : mass_erase_unlock This function combine "stm32x unlock 0" + reset to apply unlock + "stm32x mass_erase 0" In this way, it is more easier to handle the unlock sequence and makes the (annoying) reset procedure transparent. After calling mass_erase_un

[Openocd-development] [PATCH] stm32 : change returned value of mass_erase function

2010-06-01 Thread gcembed
Hello, "stm32x mass_erase" return ERROR_OK even if something goes wrong. Here is a summary of changes : * in stm32x_mass_erase : return ERROR_FLASH_OPERATION_FAILED when error detected in FLASH_SR register; * in COMMAND_HANDLER(stm32x_handle_mass_erase_command) : return the returned value of stm

[Openocd-development] [PATCH] nand : Add Freescale iMX27 nand flash controller support

2010-05-19 Thread gcembed
This patch add support of iMX27 nand flash controller. This is based on driver for imx31 nand flash controller. OOB functionality is not fully working. As in mx31 controller, mx2 NFC has a bug that swap two bytes between SPARE and MAIN buffer. I used this driver for several months and no problem