We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Two HEX files are loaded into some memory locations (using the "load <myfile.HEX>" command) Immediately after start debugging on the target board using monitor166, I can browse the loaded files using the "d 0xAddr1, 0xAddr2" command. If I start running the debug session, after stopping on a breakpoint I'm not able to see the loaded HEX files anymore. The memory now seems to be empty (actually all memory locations are filled with the value A6!). I also get the same results immediately after starting the debug session, when the "Go till main()" box is selected. Is that a normal behavior of the monitor166 or it's possibly something wrong with the external memory that I just have interfaced to the C167CR? Thank you