| commit | b3ed97a4925ff441c3c2679d01e6cdb6edc123d8 | |
| author | Rod Boyce <developer@teamboyce.co.uk> | |
| Sun, 16 Dec 2018 17:41:39 +0000 (16 17:41 +0000) | ||
| committer | Tomas Vanek <vanekt@fbl.cz> | |
| Wed, 2 Jan 2019 21:54:03 +0000 (2 21:54 +0000) | ||
| tree | 3097d70683a33e28cdfbeedb1c57d125534da2f8 | treesnapshot (tar.gz zip) |
| parent | 8f777bc1a66b5f604fde8bbdbe64206413c8aa1c | commitdiff |
NOR: lpc2000 Add support for LPC84x devices
These devices differ from LPC8xx devices in that they have a different
IAP entry point, but everything else is the same. Using Tcl to pass
different IAP entry point.
no new Clang analyser warnings and no new build sanitizers issues.
Change-Id: I2d654dd250f416e74262c0228cad8713a283402f
Signed-off-by: Rod Boyce <developer@teamboyce.co.uk>
Reviewed-on: http://openocd.zylin.com/4684
Reviewed-by: Jean-Christian de Rivaz <jcamdr70@gmail.com>
Tested-by: jenkins
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
These devices differ from LPC8xx devices in that they have a different
IAP entry point, but everything else is the same. Using Tcl to pass
different IAP entry point.
no new Clang analyser warnings and no new build sanitizers issues.
Change-Id: I2d654dd250f416e74262c0228cad8713a283402f
Signed-off-by: Rod Boyce <developer@teamboyce.co.uk>
Reviewed-on: http://openocd.zylin.com/4684
Reviewed-by: Jean-Christian de Rivaz <jcamdr70@gmail.com>
Tested-by: jenkins
Reviewed-by: Tomas Vanek <vanekt@fbl.cz>
| doc/openocd.texi | diffblobblamehistory | |
| src/flash/nor/lpc2000.c | diffblobblamehistory | |
| tcl/target/lpc1xxx.cfg | diffblobblamehistory | |
| tcl/target/lpc84x.cfg | [new file with mode: 0644] | blob |