Hi, Can anyone explain what the Source window is for in Real-Time Debugger? Everytime I click on debug its empty and the only file I can load is main.dbg, however I have seen my asm file appear on the Source window automatically after I click on debug once just like in the Full chip simulation mode.
I suspect having your asm code to appear in the Source window after you click on debug is what's meant to happen if CW is running correctly? (My project is Absolute asm)
Is it normal/correct to have the Source window empty after you click on debug?
Hi CrasyCat, I am using a OSBDM and as soon as I click on debug, it will automatically try to connect then I just get the error message that can not erase Flash and CW just thinks its a Unknow($1301) device and I have tried this to both the QG8 and GT8 with the same result. Refer the link for more detailed error
That SDIDH == 0 && SDIDL == 0 does not find the right device but instead this bogus "Unknown($1301)" is not the problem, the problem is that the pod does not report anything from the actual target but instead constantly claims it would.
When I type
1806: 00 .
1807: 00 .
I get 00 for both register and this is after I hold the BKGD pin low while powering up the QG8, I think I am unable to enter background debug mode, therefore I can not read the register or any memory locations.
However, as soon as I click on debug CW automatically assume the Unknown($1301) device. I am wondering if its because I am unable to enter background debug mode therefore the HCS08_OpenSourceBDM_Erase_Unsecure.cmd can not be executed correctly which is causing the error?
Unfortunately, due to its simplicity, the OSBDM does tend to "carry on regardless" as opposed to generating sensible error messages when things go wrong. The unknown device is probably a catch-all in CW, done before the OSBDM even existed. I don't know what your problem is though. I think you can get this with no target at all! Don't have the time at the moment to confirm this.
Hi Peg, With the 6 pin BDM disconnected I get the "No Link To Target" message on the command window in the Debugger, which is different to when the target has been connected. Once I have the target connected the debugger execute the cmd files and attempts to erase the Flash which leads tp the error of not being able to and the Unknown($1301) device.
I have added a pull up resistor on the BKGD pin and it seems allow me to write and read and write into the register and ram location of the QG8 using the command window also shows up on the memory window, this is when I saved the Mcu1019.fpp as the Mcu1301.fpp.
When I change the Mcu1301.fpp back to its original device (NVMIF HCS908CT16_V4 0x1301), it seems that I can write value into registers and memories using the command window and appears on the Memory window HOWEVER when I try to read back the same location use DB commands on the memory window it shows all 00.
Occasionally(rarely), the debugger actually recognize its a QG8, this is what I get....
Just want to report back, I followed the DEMO9S08QG8_SCH_C.pdf and added a pull-up resistor to the BKGD pin and now I am able to read and write to the memory, registors, have tested with turn on and off LEDs on Port B.
The steps are
1. Ground BKGD pin with pull up resistor 2. Click on Debug in IDE 3. HCS08 Open Source BDM Setup window opens 4. Power off and on QG8, unground BKGD pin and connect to pin 1 of BDM port 5. click OK on the HCS08 Open Source BDM Setup window 6. Debugger loads cmd files......e.g (HCS08_OpenSourceBDM_Erase_Unsecure.cmd) 7. Error message
8.Source window loads and display main.dbg file 9. WB 0x2..0x3 0xFF 10. Able to turn on/off LEDs on Port B
I think the debugger is communicating to the QG8 to some extent but not fully functional, I still get this Unknown($1301)