| commit | 8f444e22473746710112b68eb4d923ce2f45040d | |
| author | Andrey Yurovsky <yurovsky@gmail.com> | |
| Tue, 23 Jul 2013 00:26:02 +0000 (22 17:26 -0700) | ||
| committer | Spencer Oliver <spen@spen-soft.co.uk> | |
| Thu, 15 Aug 2013 14:49:27 +0000 (15 14:49 +0000) | ||
| tree | 5337b5c2a92f17ec79a521e23d60f3cc89d8112d | treesnapshot (tar.gz zip) |
| parent | f7fed92a4a7f015c3528a14f29ece9aac6967aa9 | commitdiff |
stm32lx flash: fix flash size for Medium+ devices
Unfortunately the Medium+ density and 0x436 devices have their F_SIZE register
at a different location: 0x1FF800CC instead of 0x1FF8004C. Fix this for
the 0x427 Medium+ devices and also the 0x436 devices. Furthermore, for
0x436 devices the flash size is reported as a 0 or 1 code rather than
the size in Kb. Please see RM0038 r8 or newer for an explanation, as
noted in the comments.
Change-Id: Ie03b1e119a61f2a854bc2ccc5f90ce3e8852e272
Signed-off-by: Andrey Yurovsky <yurovsky@gmail.com>
Reviewed-on: http://openocd.zylin.com/1522
Tested-by: jenkins
Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
Unfortunately the Medium+ density and 0x436 devices have their F_SIZE register
at a different location: 0x1FF800CC instead of 0x1FF8004C. Fix this for
the 0x427 Medium+ devices and also the 0x436 devices. Furthermore, for
0x436 devices the flash size is reported as a 0 or 1 code rather than
the size in Kb. Please see RM0038 r8 or newer for an explanation, as
noted in the comments.
Change-Id: Ie03b1e119a61f2a854bc2ccc5f90ce3e8852e272
Signed-off-by: Andrey Yurovsky <yurovsky@gmail.com>
Reviewed-on: http://openocd.zylin.com/1522
Tested-by: jenkins
Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
| src/flash/nor/stm32lx.c | diffblobblamehistory |