Problems using programmer with Mega128

Hello Alvin,

because programming fails with a very new Mega128 in SPI Mode I think you selected a wrong (too high) SPI speed in your project.

rolf

@Gunther
I do not use DEFINE_FUSES in the project itself as I prefer to set the fuse bits using the programmer options in the Prommer. This problem manifests in both the external ProgBox and the Prommer called from the PED32 editor.
The previous problem you quoted is unrelated to this one, as the stated solution fixed that problem.

@Rolf
What confuses me is that this only occurs when you first program the CPU, as stated above. Once the CPU has been programmed, you can then use the ISP3 to reprogram.
I set the ProcClock to the speed of the crystal, which in my case is 7372800. According to the compiler manual the default SPI speed is set to ProcClock, but you can set the SPIClk to a different speed. I can try setting an optional SPIClk speed so it will work with the ISP3, but I'm unsure to what that speed should be as the only crystal onboard is that attached to the CPU.

Is there a difference between the ISP and ISP3 programmers when they attempt to communicate with a CPU with default factory settings, for example timeout settings, or SPI speed.

I'm wondering, since I'm still using Windows XP, could this be a Windows problem as the ISP3 is a USB2 device, whilst the ISP is a USB device.

Thanks

Alvin

Rolf,
Program fuses is definitely set. I can use the USB-ISP to program the CPU where the USB2-ISP3 fails without changing ANY programmer options at all. All I do is use Search Programmers to change between the two.

Is there a timeout difference between the 2 programmers in deciding when to fail if it has not received a response from the CPU within that specified time?

Thanks

Alvin

Rolf,
I appreciate your help. Thank you. It works.

Alvin