| commit | a7a1b93004e31eb20b318c78efaa2bc3edc17ad9 | |
| author | Andreas Färber <afaerber@suse.de> | |
| Sun, 12 Jul 2015 13:45:20 +0000 (12 15:45 +0200) | ||
| committer | Freddie Chopin <freddie.chopin@gmail.com> | |
| Fri, 20 May 2016 20:42:19 +0000 (20 21:42 +0100) | ||
| tree | 40868e9b91b97e11927987def0d254b8d3c7d8e1 | treesnapshot (tar.gz zip) |
| parent | 679ae2a98d38a42283c3962003db80d02c07406c | commitdiff |
lpcspifi: Fix SWD support for LPC43xx
When using SWD rather than JTAG transport, the lpcspifi driver complains:
Error: Device ID 0x0 is not known as SPIFI capable
Error: auto_probe failed
This is because target's JTAG tap->idcode is zero for SWD.
Drop this check completely and hardcode the addresses for now. Neither
the JTAG TAPID nor the SWD IDCODE are unique enough to detect the exact
chip model and thereby its memory map.
Change-Id: Ic230e3e989a3e1f1a5b3bae68bdb34e5ef55d392
Signed-off-by: Andreas Färber <afaerber@suse.de>
Reviewed-on: http://openocd.zylin.com/3089
Tested-by: jenkins
Reviewed-by: Freddie Chopin <freddie.chopin@gmail.com>
When using SWD rather than JTAG transport, the lpcspifi driver complains:
Error: Device ID 0x0 is not known as SPIFI capable
Error: auto_probe failed
This is because target's JTAG tap->idcode is zero for SWD.
Drop this check completely and hardcode the addresses for now. Neither
the JTAG TAPID nor the SWD IDCODE are unique enough to detect the exact
chip model and thereby its memory map.
Change-Id: Ic230e3e989a3e1f1a5b3bae68bdb34e5ef55d392
Signed-off-by: Andreas Färber <afaerber@suse.de>
Reviewed-on: http://openocd.zylin.com/3089
Tested-by: jenkins
Reviewed-by: Freddie Chopin <freddie.chopin@gmail.com>
| src/flash/nor/lpcspifi.c | diffblobblamehistory |