Hello, Am Dienstag, 27. Juli 2010, 01:19:01 schrieb David VomLehn: > Alexander, and sense of how far it gets before hanging, first character, a > bunch of characters, etc. Here is the console output from that sam-ba tool: > -I- Waiting ... > -I- TCL platform : Linux > -I- SAM-BA CDC 2.9 rc6 on : linux > -I- Connection : /dev/ttyUSB0 (target(comType) = 1) > -I- Board : at91sam9263-ek > -I- Traces Level : 4 > -I- target(handle) : file5 > Read device Chip ID at 0xfffff240 --- get 0x00000000 > Read device Chip ID at 0xffffee40 --- get 0x019607a2 > -I- Found processor : at91sam9263 (Chip ID : 0x019607a2) > -I- External RAM Settings : extRamVdd=1, extRamType=0, extRamDataBusWidth=32, extDDRamModel=0 > -I- Loading applet isp-extram-at91sam9263.bin at address 0x301000 And here it got stuck. I can't say much about the protocol though it is described in the controller's manual, something about xmodem is stated, but I'm not much into that. Summarized sam-ba talks to an application stored in the internal ROM of the controller. As you can see, at least some data is written and read, because i could detect which processor the device has attached. But the problem arises if a binary is downloaded into sram of the controller. Oh, and if I retry to start sam-ba after it got stuck first, if stop at the line "-I- target(handle) : file5" where, I guess, it writes/reads to the device first in that session. > > Alexander, does the 2.6.35-rc6 kernel also have this problem? Yes, I'm currently running 2.6.35-rc6 and the problem still occurs. Best regards, Alexander -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
