flash/stm32lx: mention explicitly that this driver covers STM32 L0 and L1
this is to avoid confusion with STM32 L4, L4+ and L5 families also: - a warning message is changed to error - stm32l0x and stm32l1x aliases has been created to permit the usage of either names Change-Id: If3f16d2a3b7d1369959aa7407da37a9076ea91d7 Signed-off-by: Tarek BOCHKATI <tarek.bouchkati@gmail.com> Reviewed-on: http://openocd.zylin.com/5437 Reviewed-by: Marc Schink <dev@zapb.de> Tested-by: jenkins Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
This commit is contained in:
parent
6dfcc3f5a5
commit
0a11537b32
|
@ -6852,7 +6852,7 @@ stm32h7x option_write 0 0x20 0x8000000 0x8000000
|
|||
@end deffn
|
||||
|
||||
@deffn {Flash Driver} stm32lx
|
||||
All members of the STM32L microcontroller families from STMicroelectronics
|
||||
All members of the STM32L0 and STM32L1 microcontroller families from STMicroelectronics
|
||||
include internal flash and use ARM Cortex-M3 and Cortex-M0+ cores.
|
||||
The driver automatically recognizes a number of these chips using
|
||||
the chip identification register, and autoconfigures itself.
|
||||
|
|
|
@ -756,7 +756,7 @@ static int stm32lx_probe(struct flash_bank *bank)
|
|||
}
|
||||
|
||||
if (n == ARRAY_SIZE(stm32lx_parts)) {
|
||||
LOG_WARNING("Cannot identify target as a STM32L family.");
|
||||
LOG_ERROR("Cannot identify target as an STM32 L0 or L1 family device.");
|
||||
return ERROR_FAIL;
|
||||
} else {
|
||||
LOG_INFO("Device: %s", stm32lx_info->part_info.device_str);
|
||||
|
|
|
@ -109,6 +109,10 @@ proc stm32f3x args { eval stm32f1x $args }
|
|||
proc stm32f4x args { eval stm32f2x $args }
|
||||
proc stm32f7x args { eval stm32f2x $args }
|
||||
|
||||
# stm32lx driver supports both STM32 L0 and L1 devices
|
||||
proc stm32l0x args { eval stm32lx $args }
|
||||
proc stm32l1x args { eval stm32lx $args }
|
||||
|
||||
# stm32wb uses the same flash driver as the stm32l4x
|
||||
proc stm32wbx args { eval stm32l4x $args }
|
||||
|
||||
|
|
Loading…
Reference in New Issue