I have a project in codewarrior v10.2 Yesterday it was programming fine, I made a change to one header file in a barebones application, and recompiled then I started getting this error.
Download Task Failure:Error: Couldn't write flash driver to target.Coldfire GDI Protocol Adapter : An error occurred while trying to write memory. Bus error while reading/writing memory.Do you want to continue?
Continuing fails, which is not much of a surprise, but I can't seem to find anything to change why this is happening, nor what I can change that's ever related to this. I have tried reinstalling the drivers for the programmer and am at a loss for whatelse to do. I tried having my coworker program this board, and he has no problem, which means that it is either a system or codewarrior problem. Any help would be greatly appreciated
When you say that a coworker can program the same board, is it because they're using a separate workstation, copy of CodeWarrior, and emulator probe?
If so, try the following: move your emulator probe to the other system and see if it experiences a failure. Likewise, see if the other probe--moved to your system--works.
At a minimum, that will eliminate a sudden failure on the part of the probe from being the problem.
They have a separate workstation and all materials, but we have a shared repo of code and he is able to put the code on the same platform with the same probe.
I did make some progress, I started a brand new workspace with a new barebones project, and was able to get the programmer to talk to the chip, so it is likely some sort of environment issue right?
Thanks for your help,
It does sound like an environment issue. However, I do not understand how changing a header file would upset the probe driver. What header file did you change?
It was a system file for our project, I actually changed a setting for the PLL, because we changed the crystal. I did a system restore last night due to some other problems with my computer last night, and now the problem has changed. I can succesfully download, but about ten instructions into debugging it locks up without any indication of why. This is the boot strap from the project, and it locks on the last instruction.
/* disable interrupts */ move.w #0x2700,sr /* Setup initial stack */ move.l #__SP_AFTER_RESET, a7 /* Initialize RAMBAR: locate SRAM and validate it */ move.l #__RAMBAR + 0x21,d0 movec d0,RAMBAR /* Initalize IPSBAR */ move.l #__IPSBAR,d0 andi.l #0xC0000000,d0 // need to mask add.l #0x1,d0 move.l d0,0x40000000 /* Initialize FLASHBAR */ move.l #__FLASHBAR,d0 andi.l #0xFFF80000,d0 // need to mask add.l #0x61,d0 movec d0,FLASHBAR /* Setup final stack pointer */ lea _SP_INIT, a7 /* setup A6 dummy stackframe */ movea.l #0, a6 link a6, #0 /* Setup A5 SDA pointer */ lea _SDA_BASE, a5 /* Copy bootloader code and initialized data to RAM */ lea _BOOT_CODE_ROM_START, a0 lea _BOOT_CODE_RAM_START, a1
Again, any help is greatly appreciated,