well… i had verified the connection, interface and power many a times (rather, each time when i try to make it on) but the problem is still the same.
Even i burned my testing code into the same chip via the virtual serial port using independent flash utility (flash Magic )… it run fine !
thus we can say that the device arm-usb-ocd is working properly … then what other options do i have to recheck the software settings especially for JTAG interface (instead of modifying the .cfg file )??
I read this topic, but with the available info I can only speculate. I can’t see anything about how mayur connects ARM-USB-OCD nor what is his target board, nor what is his power supply, what voltage levels he measure on the microcontroller core etc.
I see he only mention LPC2138 learning kit which he made himself, no schematic, none info if there are pullups pulldowns on the JTAG lines, is the JTAG enabled/disabled? are the Vcc levels within the JTAG working range?
"6. when i used the par-port wiggler device with IAR IDE to interface with
the same board(lpc 2138) … it worked fine!! "
OpenOCD supports Wiggler too, so why mayur don’t try it? then it will be clear if something is wrong with ARM-USB-OCD or he do something wrong with the openOCD installation/setup?
very nice to see u replying. well… now i’ll again try explain you what u may want…
my core power requirement is +5v dc . I was using +5v dc power supply but later on i powered the board through the arm-usb-ocd device itself. And before connecting it through usb hub it supplies +4.78 v dc and after… +5.15v dc.
i don’t understand what is to be done to enable the JTAG ? is there any special provision ?
i installed and tried to interface the Wiggler device with openocd also but it prompted the same error msg.
further, i was succeded in downloading the code through the virtual COM port provided on the arm-usb-ocd device itself.
now when the com port interface is ok , what may go wrong with JTAG interface ?
and even if i dont connect the JTAG connector to the board, still get exactly the same error !! so how do can we say that anything gone wrong with the target hardware (board) ?
well… there might go something wrong with my installation procedure … but i had followed exactly the same steps which are mentioned in the pdf document in the CD
please take a glance over my previously posted threads to read the exact error messages i’m getting…
i don’t understand what is to be done to enable the JTAG ? is there any special provision ?
this says it all, you try to build LPC2138 board yourself but didn’t read LPC2138 datasheets and you don’t know how to enable the JTAG port
I asked you above questions about your schematic, how do you connect the JTAG to LPC2138, are there pullups pulldowns on the JTAG lines?
I don’t ask what is your power supply on the power jack but on your microcontroller i.e. what are the voltage levels on your LPC2138 ports.
mifi: do you understand where is the problem now?
we got at least 2-3 e-mails per week with content like: “hi, I bought your ARM-JTAG and I have never used linux before but want to build linux kernel for my SAM7X256 board, can you teach me how to do this?”
frankly I don’t know what to tell our peoples how to answer questions like this.
well well well… i apologize for that kind of answer from me…!
actually i wanted to say that i had already enabled the JTAG ( by installing the JTAG jumper ) on my board . but if there is any other provision for it on the " arm-usb-ocd " device then i dont know about that.
and even if i dont connect the device to my board, i get the same error msg.
soon i’ll send you the schematics of my board .
i hope you will be kind enough to consider my point .