cortexm: Fixed the probing for LMI devices (both Cortex-M3 and Cortex-M4)
Other routines that were firing in front of lmi_probe were putting the devices into bad state and causing a plethora of issues
This commit is contained in:
parent
a561e71fc3
commit
9d43ade05c
|
@ -460,6 +460,7 @@ bool cortexm_probe(ADIv5_AP_t *ap)
|
|||
PROBE(rp_probe);
|
||||
PROBE(lpc11xx_probe); /* LPC8 */
|
||||
} else if (ap->ap_partno == 0x4c3) { /* Cortex-M3 ROM */
|
||||
PROBE(lmi_probe);
|
||||
PROBE(ch32f1_probe);
|
||||
PROBE(stm32f1_probe); /* Care for other STM32F1 clones (?) */
|
||||
PROBE(lpc15xx_probe); /* Thanks to JojoS for testing */
|
||||
|
@ -468,6 +469,7 @@ bool cortexm_probe(ADIv5_AP_t *ap)
|
|||
PROBE(lpc11xx_probe); /* LPC24C11 */
|
||||
PROBE(lpc43xx_probe);
|
||||
} else if (ap->ap_partno == 0x4c4) { /* Cortex-M4 ROM */
|
||||
PROBE(lmi_probe);
|
||||
/* The LPC546xx and LPC43xx parts present with the same AP ROM Part
|
||||
Number, so we need to probe both. Unfortunately, when probing for
|
||||
the LPC43xx when the target is actually an LPC546xx, the memory
|
||||
|
@ -486,7 +488,6 @@ bool cortexm_probe(ADIv5_AP_t *ap)
|
|||
}
|
||||
/* Info on PIDR of these parts wanted! */
|
||||
PROBE(sam3x_probe);
|
||||
PROBE(lmi_probe);
|
||||
PROBE(ke04_probe);
|
||||
PROBE(lpc17xx_probe);
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue