Added development.
It seems when using SEGGER JLINK (the one on the board) that memory outside of certain regions does not READ.
Attachment 3563
Reading 4000'0300 (SCU_CLK or something around it) for 20 bytes OK and has data. Read same for 21 bytes: NO. No error description other than Could Not Read Memory.
Reading 4001'1000 (SCU_ANALOG) for anything more than 2 bytes fails. 2 bytes shows the correct default value.
IT SEEMS TO ME... that for some reason JLINK (not Keil) is only able to read specifc bytes from the chip. When Keil asks JLINK to show memory data it probably asks for 16+ bytes at a time, meaning the JLINK is probably telling Keil "could not read memory" and Keil shows this to me as "??". If I could somehow get Keil to read only 2 bytes, it seems that would work.
Seems like default behavior should be that when memory can't be read by Segger that it still reports the things in can read. Could this be some memory protection that isn't being disabled in the startup file?
It seems when using SEGGER JLINK (the one on the board) that memory outside of certain regions does not READ.
Attachment 3563
Reading 4000'0300 (SCU_CLK or something around it) for 20 bytes OK and has data. Read same for 21 bytes: NO. No error description other than Could Not Read Memory.
Reading 4001'1000 (SCU_ANALOG) for anything more than 2 bytes fails. 2 bytes shows the correct default value.
IT SEEMS TO ME... that for some reason JLINK (not Keil) is only able to read specifc bytes from the chip. When Keil asks JLINK to show memory data it probably asks for 16+ bytes at a time, meaning the JLINK is probably telling Keil "could not read memory" and Keil shows this to me as "??". If I could somehow get Keil to read only 2 bytes, it seems that would work.
Seems like default behavior should be that when memory can't be read by Segger that it still reports the things in can read. Could this be some memory protection that isn't being disabled in the startup file?