**** BEGIN LOGGING AT Tue Mar 23 02:59:57 2010 **** BEGIN LOGGING AT Tue Mar 23 11:58:15 2010 Mar 23 14:14:07 hi Mar 23 14:14:25 someone alive? Mar 23 14:21:19 no. Mar 23 14:41:52 :D Mar 23 14:43:18 anyone knows why it gaves this err mess on this? Mar 23 14:43:24 > reset Mar 23 14:43:25 JTAG tap: s3c2440.cpu UNEXPECTED: 0x000000ff (mfg: 0x07f, part: 0x0000, ver: 0x0) Mar 23 14:43:25 JTAG tap: s3c2440.cpu expected 1 of 1: 0x0032409d (mfg: 0x04e, part: 0x0324, ver: 0x0) Mar 23 14:43:25 Trying to use configured scan chain anyway... Mar 23 14:43:25 s3c2440.cpu: IR capture error; saw 0x0f not 0x01 Mar 23 14:43:26 error: -100 Mar 23 14:43:58 my openocd.cfg is more than basic Mar 23 14:44:23 it has only sources of interface board and target Mar 23 14:44:39 i'm not sure what i need to add Mar 23 14:45:19 haven't found yet a openocd.cfg file spcific for mini2440 Mar 23 14:46:46 cat openocd.cfg Mar 23 14:46:46 source [find interface/olimex-arm-usb-ocd.cfg] Mar 23 14:46:46 source [find board/mini2440.cfg] Mar 23 14:46:46 source [find target/samsung_s3c2440.cfg] Mar 23 14:46:46 ft2232_latency 10 Mar 23 14:47:04 what i've missed? Mar 23 14:49:26 hm, no clue. Mar 23 14:49:34 try the openocd mailinglist Mar 23 14:49:45 if you don't get an answer here Mar 23 14:52:32 thks Mar 23 15:19:55 seems ok if exclude source [find target/samsung_s3c2440.cfg] Mar 23 15:20:37 > reset halt Mar 23 15:20:37 target state: halted Mar 23 15:20:37 target halted in ARM state due to debug-request, current mode: Supervisor Mar 23 15:20:37 cpsr: 0x400000d3 pc: 0x00000000 Mar 23 15:20:37 MMU: disabled, D-Cache: disabled, I-Cache: disabled Mar 23 15:21:00 finally the light at the end of tunnel...:))) Mar 23 20:59:47 anyone alive? Mar 23 21:03:57 heck...nobody here? Mar 23 21:04:53 3th time when i come here and no one say nothing... **** ENDING LOGGING AT Wed Mar 24 02:59:57 2010