The latest batch of my production boards changed to Rev C of the SAM7S64 and I can no longer get SAMBA boot to work. I haven't dug into it too thoroughly yet, but wanted to check if anyone else has seen a problem.

I am using SAMBA boot for the initial code load in production through the USB port. It is a custom board design, but has been stable and working for a couple of years. With the rev C parts, the USB port does not even enumerate.

I can connect through the SAM-ICE debugger and I can see that the SAMBA-boot code is being loaded into flash when the TST pin is pulled high at power up. I also have my own bootloader based on the SAMBA boot source code, and that works fine if I load it through the debugger.

Has anyone else tried using SAMBA boot through the USB port on rev C silicon, and if so were you able to get it working?

Thanks.

Tom

The complaints about the Rev C, seem in general to revolve around the clocks and the flash. Suggest you double check the oscillator is clocking, and at the rate you'd expect.

Thanks for the suggestion. The clock is not running, but I don't know if that means the code is not executing properly or there is a clock problem. I also don't think the difference means much to me, as both problems mean I can't use SAMBA boot.

The clock does seem to run fine with my application code.

Tom

I have the same problem. Did you ever get any resolution on this?

I finally got a chance to take a look at it, but without much success. The bootloader code is definitely loading correctly, and it starts to execute but heads off into invalid memory areas. The bootloader binary is significantly different for rev C from rev B. It looks like they changed the ROM and got an error in it, but it's hard to believe that got through testing and release without being noticed.
I guess I'll be programming by boards throught the emulator until I get a better answer.