Jennie:
Yes, that helped very well. Thank you. After following the path to get to that checkbox, I unchecked it, and then the Debugger started up, programmed my code into the processor, and I was able to run.
However....
I had been experimenting with writing data out of the serial port using the QB8 device. Now, with the SH8 device in place, the communications seemed off. After some testing, I found that I had to change my SCIBDL baud register from 0x1B to 0x35 to get good communications at 9600 baud.
Since the SCIBDL value was originally calculated based on the BUSCLK of the QB8 device, I tried loading a small Assembler program into the SH8 that allows me to toggle an output bit for 10 CPU cycles high/low to then derive the BUSCLK frequency to see if that frequency had changed from the QB8 device. This small program had worked fine on the QB8 device.
On invoking the debugger with the SH8 device and this small BUSCLK test program, I again got the error where it couldn't read the Trim values, so I performed the same procedure from your video to un-check the "Calculate Trim and Program the Non-Volatile Trim Register" checkbox, but the debugger still would not start up, giving me the same "Error measuring trim values" error.
TWO questions:
1) What am I doing incorrectly?
2) Will this type of issue cause a problem down the line when these SH8 devices have to be programmed on our Production floor for our final product?