Ok, looks good, id is correct. Your cfg file still contains some things
specific to the example:
The RSTEN and RST instructions may not be appropriate to your chip, so I'd
suggest to remove that (or check your datasheet). But in the very same way you
may configure your flash, see below.
Since this chip is quite new, it's not know to the driver automatically, so you
need to use the 'stmqspi set' command with the parameters as indicated in the
docs (or just do a 'stmqspi set' to get a list of the required parameters).
There are some sanity checks implemented for the parameters with sensible error
messages ... You will still see the initial warning "Unknown ..." as the
autoprobe fails, but this can be safely ignored then.
As your flash chip has more than 16 Mbytes, you will need to care about the
addressing: Either use the 'standard' read/page write commands 0x03/0x02 and
set the flash to 4-byte mode via a specific command, or use the 4-byte address
commands (if any, please check datasheet).
---
** [tickets:#211] Enable break points on QSPI debugging + OpenOCD**
**Status:** new
**Milestone:** 0.9.0
**Created:** Thu Nov 29, 2018 07:45 AM UTC by shaalik
**Last Updated:** Tue Dec 11, 2018 11:56 AM UTC
**Owner:** nobody
Hi,
We were able to debug from QSPI NOR flash on custom stm32H7 + NOR board, and
possible to do step in and step over. However it is not possible to set or
clear break points on run time. How can we enable the break points on QSPI NOR
flash debugging
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/openocd/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/openocd/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
