This is an automated email from Gerrit. Andrey Yurovsky ([email protected]) just uploaded a new patch set to Gerrit, which you can find at http://openocd.zylin.com/1790
-- gerrit commit 6a7934e3810a29e7425a17b7b403ad426b7f5cb9 Author: Andrey Yurovsky <[email protected]> Date: Fri Nov 1 14:29:17 2013 -0700 stm32l flash: add another device ID Add device ID 0x437, a dual-bank part with 512KB total. This one used the Medium+/HD flash size register to read the flash size in Kb rather than the 0/1 code in the Medium+ parts. Signed-off-by: Andrey Yurovsky <[email protected]> Change-Id: I870fe3bb1b473939b7211c3b2edb44b4b3643648 diff --git a/src/flash/nor/stm32lx.c b/src/flash/nor/stm32lx.c index b1c8eca..b8b5306 100644 --- a/src/flash/nor/stm32lx.c +++ b/src/flash/nor/stm32lx.c @@ -550,6 +550,12 @@ static int stm32lx_probe(struct flash_bank *bank) first_bank_size_in_kb = 192; stm32lx_info->has_dual_banks = true; break; + case 0x437: + /* Dual bank, high density */ + max_flash_size_in_kb = 512; + first_bank_size_in_kb = 192; + stm32lx_info->has_dual_banks = true; + break; default: LOG_WARNING("Cannot identify target as a STM32L family."); return ERROR_FAIL; @@ -558,7 +564,8 @@ static int stm32lx_probe(struct flash_bank *bank) /* Get the flash size from target. 0x427 and 0x436 devices use a * different location for the Flash Size register, please see RM0038 r8 or * newer. */ - if ((device_id & 0xfff) == 0x427 || (device_id & 0xfff) == 0x436) + if ((device_id & 0xfff) == 0x427 || (device_id & 0xfff) == 0x436 || + (device_id & 0xfff) == 0x437) retval = target_read_u16(target, F_SIZE_MP, &flash_size_in_kb); else retval = target_read_u16(target, F_SIZE, &flash_size_in_kb); @@ -779,6 +786,10 @@ static int stm32lx_get_info(struct flash_bank *bank, char *buf, int buf_size) } break; + case 0x437: + device_str = "STM32L1xx (Medium+/High Density)"; + break; + default: snprintf(buf, buf_size, "Cannot identify target as a STM32L1"); return ERROR_FAIL; -- ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
