**** BEGIN LOGGING AT Fri Nov 20 03:00:07 2009 Nov 20 10:16:32 Hello Nov 20 10:17:26 is there any standard or specification detailing JTAG connector?, for instance the common 20pins one (like those used in olimex jtag dongles or similar) Nov 20 14:12:52 anyone familiar with: Unknown command: halt 0 Nov 20 14:13:06 getting that from issuing openrd_init .. Nov 20 14:13:35 where do you get that? Nov 20 15:40:40 Kebianizao|work: when trying to flash uboot Nov 20 15:42:02 issuing the command like: sudo openocd -f /usr/local/share/openocd/scripts/board/openrd.cfg -c openrd_reflash_uboot Nov 20 15:42:11 what openocd version? Nov 20 15:42:24 0.3.1 Nov 20 15:42:38 maybe that script is incorrect Nov 20 15:42:53 umm Nov 20 15:43:02 maybe you need -c ocd_init Nov 20 15:43:04 same with 0.4 from yesterday Nov 20 15:43:39 which commands does openocd kow further then the funtions defined in the .cfg dcripts? Nov 20 15:43:42 script Nov 20 15:44:17 I don't understand that question, but what I meant is that you need to call ocd_init before you can call any other ocd command Nov 20 15:44:27 oh, with ocd_init I get something new: Nov 20 15:44:55 Warn : memory write caused data abort (address: 0xd000140c, size: 0x4, count: 0x1) Nov 20 15:45:03 Runtime error, file "/usr/local/share/openocd/scripts/board/openrd.cfg", line 40: Nov 20 15:45:24 where line 40 is: mww 0xD000140C 0x00000A33 # DDR SDRAM Timing (High) Register Nov 20 15:46:22 oh, nevermind that one, after rebooting hte board I am back to the original error: Nov 20 15:46:35 Error: unknown NAND flash device found, manufacturer id: 0x00 device id: 0x00 Nov 20 15:46:52 umm, looks like you have a problem in your hardware Nov 20 15:46:59 rly? Nov 20 15:47:04 or you are calling for the functions incorrectly Nov 20 15:47:18 try increasing debug output with -d3 Nov 20 15:48:00 Iwas using "-c init -c openrd_reflash_uboot" and got the question here, why I use that init .. Nov 20 15:48:27 without the init (or the same with ocd_init as you suggested) I get this manufacturer error Nov 20 15:48:42 -c init -c openrd_init -c openrd_reflash_uboot Nov 20 15:48:57 otherway: without the init the commands (like halt 0) are not recognised Nov 20 15:49:07 umm, openrd_init is done in openrd_reflash_uboot Nov 20 15:49:12 with init I get the unknown manufacturer Nov 20 15:49:24 yes, it gets called anyway Nov 20 15:49:30 yes, that what I meant with ocd_init, just I failed to remember its correct name Nov 20 15:49:36 ohok Nov 20 15:50:04 try loading uboot instead: openrd_load_uboot Nov 20 15:50:33 butL: without calling the ocd_init or just init I always get the "halt 0" no defined. and my question above refered to that: where is init or ocd_init defined (not calling openrd_init ..) Nov 20 15:51:18 phaidros: I suggest taking a look a openocd documentation Nov 20 15:51:26 hm Nov 20 15:51:28 read about the initialization Nov 20 15:51:33 (of openocd) Nov 20 15:51:38 ok Nov 20 15:51:50 the nand issue could be probably a hardware or script bug Nov 20 15:51:56 ok Nov 20 15:52:01 feel free to raise the topic on the openocd ML Nov 20 15:52:10 I acutally did :) Nov 20 15:53:56 oh, really :) Nov 20 15:54:02 * Kebianizao|work checks Nov 20 15:54:51 could you post here (using a paster) the output of the command with -d3 Nov 20 16:03:23 Kebianizao|work: Nov 20 16:03:32 http://pastie.org/707727 Nov 20 16:06:26 umm, I'm sorry that's too platform dependent and I don't know that one enough Nov 20 16:06:38 but actually sending that to the list may help Nov 20 16:11:57 ok, thanks alot! **** ENDING LOGGING AT Sat Nov 21 02:59:57 2009