Here is where I'm at.

SAMBA GUI 2.11, SAMBA ROM 1.17.

9260 chip. Not a development kit.

64 Mb SDRAM and 128 Mb NAND on combo die, no dataflash.

I have modified SAM-BA and it works peachy with JTAG. I don't want a JTAG on final board - board is too small (am I nuts?).

SAMBA on ROM comes up. I can connect to it with SAMBA GUI using either DBGU or USB Device port.

DBGU works just as peachy as JTAG, just slower.

USB does not work.

I can do the low level init fine. Same code, same settings as my sucessful JTAG code. All modified memory reads the same after startup.

I have access to SRAM with SAMBA GUI. I can load/readback/verify a 4K file just fine. I can do it many times very quickly with no errors.

BUT...

I can not reliably init / load applets to SDRAM. SAMBA hangs and needs to be killed. I have compiled dozens of variations to the extram applet, all to the same result.

I can use JTAG (Segger J-Mem) to survey the memory after hang. It looks correct. It appears the applet runs correctly with no errors. The status and end of program messages are there and correct.

WHY, then, is it crashing? Do we have an internal TCL issue? Is there something I'm missing about addressing higher memory from the SAMBA ROM program? Does the Remap thing work differently than with JTAG and DBGU?

Pretty much the same thing on XP, Vista and Fedora 16 (all 2.11, all pretty much the same issue)

I have read several posts here. Seems USB is problematic, but did not find exact same problem either.

Please - sage advice from the veterans here - am I missing the simplest thing ever from the data sheet, or is SAMBA over USB a lost cause??

TIA.

- NBB