Paul, check your current configuration file (usually project.ini). Also the file name (with path) is present in the debugger title bar. In the .ini file, search for Target=..... where the right side is the current target to be used (e.g. 'sim' for simulator). Maybe this is (somehow) set in a wrong way on your system. What you wanna have there for ICD12 is Target=icd12 You may send my your .ini file offlist if you want so I can have a look. Erich > -----Original Message----- > From: Paul Johnson [mailto:] > Sent: Wednesday, September 11, 2002 6:11 PM > To: > Subject: RE: [68HC12] Problems programing flash on M68KIT912DP256 with > BDM Multilink/Metrowerks > I don't know if this applies, but every morning I have to go through quite a > routine to program flash on my 912DT128A. It turns out that the first time > the debugger runs (on my system) it has reset the target to simulator. I > then get dozens of errors as it tries to flash the simulator. When I can > finally get it to stop, I have to reset the target to IDC12, then go and set > the MCU type, Communication speed, etc. Then I often need to set the target > again. It's not that it is "wrong" but apparently something that happens > when the dialog closes the second time sets some value that allows the > system to work. Note that the MCU type and communication speed are also > correct in the dialog, but I have to open the dialog and set them anyway for > the system to start working. > > After this hair tearing process, the debugger will work fine all day, until > I reboot again. > > Paul > > > -----Original Message----- > > From: djsimpson100 [mailto:] > > Sent: Friday, August 30, 2002 5:23 AM > > To: > > Subject: [68HC12] Problems programing flash on M68KIT912DP256 with BDM > > Multilink/Metrowerks > > > > > > Hi all, > > > > I am having problems programming the flash on the MC9S912DP256. I am > > using Codewarrior HC12 V1.2 and the P&E BDM Multilink which came with > > the Motorola M68KIT912DP256. > > > > If I load the Fibo Flash example, the debugger stalls at at the 60% > > mark in executing the postload cmd file, and the code is not written > > to flash. This also seems to crash the BDM Multilink as I cannot > > write to or edit the RAM. > > > > If I load the the LEDS-EVB_DP256-RAM example, everything works fine > > (ie I can single step, examine/change ram etc until I access the > > FLASH menu item under the ICD-12 menu. > > > > When I look at the Flash, under the ICD-12 menu item, all the flash > > is at the same address as shown below when loading the Leds-EVB-RAM > > example. > > > > Name Start End State > > > > > > EEPROM 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_4000 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_C000 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_3 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_2 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_1 00000400-00000FFF Enabled/Blank/Unprotected > > FLASH_0 00000400-00000FFF Enabled/Blank/Unprotected > > > > > > If I try and do anything to the Flash I get an error > > message "Operation failed on FLASH_x flash module" (where x is the > > module I tried to program/disable/protect). > > > > Some times the addresses given in the table are different, and > > sometimes the MCU speed was not show correctly as 8.00 MHz. (Once was > > 0 MHz, and once was 49.9MHz) > > > > The BDM appears to work, as I can run / debug etc the leds-EVB-RAM > > example. I have tried this on two computers, both with the same > > result. > > > > I was then able to try a Motorola SDI pod, and with the same EVB and > > same computer I am able to correctly program and access the Flash. > > > > Any help would be appreciated. > > > > Thank you! > > > > David J Simpson > > > > > > > > > > -------------------- > > > > > > > > ">http://docs.yahoo.com/info/terms/ > > > > > > > -------------------- > > ">http://docs.yahoo.com/info/terms/ |