Post by thread:[PIC]: ICD question

Did I do the tag right? :-) Why can't the folks at Microchip get it through their heads that programming EVERY location when you're only using a few hundred is a real waste of time? I'm working on a small section of a program. I set the program range to 0x0000 - 0x200. As long as the debug box is checked, the damned thing wants to program the WHOLE chip, which takes about forever. If the debug box is unchecked, I have to unplug the 'phone' cable while running, and reconnect it (and push the reconnect button) to program. This is nuts, or am I just missing something obvious? -- Phillip M. Vogel, President | "It's not what you've been taught, Bartal Design Group, Inc. | it's what you've learned." (me) 318 Marlboro Road | +1-201-567-1343 FAX:+1-201-568-2891 Englewood, NJ 07631 USA | spam_OUTphillipTakeThisOuTbartal.com

If you check the "erase all before programming" box the ICD will write just your code and the debug code. It's much faster! Friendly Regards Octavio Nogueira =================================================== .....nogueiraKILLspam@spam@propic2.com ICQ# 19841898 ProPic tools - low cost PIC programmer and emulator http://www.propic2.com =================================================== {Original Message removed}

<x-flowed>At 06:08 PM 6/6/00 -0300, you wrote: >If you check the "erase all before programming" box >the ICD will write just your code and the debug code. >It's much faster! > >Friendly Regards > >Octavio Nogueira While this is true, I don't think this is what Phillip meant. The ICD doesn't write to blank locations when you check "erase all before programming", but it writes all the locations in your program whether the bytes have been changed or not. It takes a lot longer to write a byte than to read it, so this slows things down a lot. From what I've heard, the PicStart Plus does the same thing. Except when working with 16F87X parts, I use an old ITU programmer. The software that came with it does this same thing... writes every location that has program in it whether it has changed or not. Instead, I'm using the command line program PP. It only writes to locations that have changed. Generally, when I'm debugging code, it will write my changes into the chip in under 2 seconds. Having been spoiled by this, using the ICD is a bit of a pain. John Hansen </x-flowed>

Trying to figure out if my "homebrew" ICD is working. I'm using MPLAB 5.4 and the ICD 16f876 is programmed with the code that came with that release (2.30.01). Anyway, I've got communication with the ICD, but when I click on "options" then "self test", I get an error that says "incorrect MCLR pin high voltage. Check ICD pin 1.0xA7". Is this error because I don't have the ICD connected to a host, or do I have a problem with my circuit. BTW, I am getting 13 volts from the charge pump/regulator, and the power switching transistors seem to be working. I also checked the VPP signal to the 16F876 via the voltage divider. The voltage is correct there too. Can anyone give me some guidance? Thanks and regards, Mike M. Palm Harbor, FL -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics

Hi! I have large (>2k) code, so my GOTO's and CALL's will probably be longer than 2k too.Could someone tell me, why I cant get my program to stop at breakpoint when I use RUN command on ICD? When I stop, program is somewhere it shouldn't be. Program gets to MAIN when I single step through it? It also works with MPSIM. Is it some bug or limitation of ICD or am I just doing something wrong? TIA, Samo ORG 0x000 ; processor reset vector nop movlw high INIT ;get HI byte of TABLE address movwf PCLATH ;to PCLATH=HI part of program counter goto INIT ; go to begginning of program MAIN ;BREAKPOINT!!!!!! nop goto MAIN ORG .3000 INIT nop movlw high MAIN ;get HI byte of MAIN address movwf PCLATH ;to PCLATH=HI part of program counter goto MAIN ;initialisation is done, jump to MAIN loop -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics

> I have large (>2k) code, so my GOTO's and CALL's will probably be longer > than 2k too.Could someone tell me, why I cant get my program to stop at > breakpoint when I use RUN command on ICD? When I stop, program is somewhere > it shouldn't be. Program gets to MAIN when I single step through it? It also {Quote hidden}> works with MPSIM. Is it some bug or limitation of ICD or am I just doing > something wrong? > > TIA, Samo > > ORG 0x000 ; processor reset vector > nop > movlw high INIT ;get HI byte of TABLE address > movwf PCLATH ;to PCLATH=HI part of program counter > > goto INIT ; go to begginning of program > > MAIN > > ;BREAKPOINT!!!!!! > nop > goto MAIN > > ORG .3000 > > INIT > nop > > movlw high MAIN ;get HI byte of MAIN address > movwf PCLATH ;to PCLATH=HI part of program counter > > goto MAIN ;initialisation is done, jump to MAIN loop I don't know anything about the ICD, but this code looks OK to me. I don't understand why you put a NOP at 0, but it shouldn't cause any harm either. Maybe that's an ICD thing? Take a look at my GJUMP and related macros in STD.INS.ASPIC at http://www.embedinc.com/pic. GJUMP is a convenient wrapper for jumping to code that can be on another page. ***************************************************************** Embed Inc, embedded system specialists in Littleton Massachusetts (978) 742-9014, http://www.embedinc.com -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics

All, I have developed some code for an in house test system using the 16F877 and the ICD1 system from Microchip. When I run my code using the ICD, all works as planned. However, as soon as I disable the ICD executive code so that it runs in stand alone mode, it doesn't work. I've single stepped through it in ICD mode, and see nothing that would cause it to stop working. So my geuss is I'm missing something when turning off the ICD mode. What I do to disable it is to uncheck the checkbox in the ICD options dialog near the bottom that says 'Enable Debug Mode'. When I do this, and reprogram the chip, it should run in stand alone mode, correct? Does anyone have any ideas or clues as to what I'm doing wrong? If so, please reply to me ASAP at jpaulKILLspamappliedmems.com. I have to get my firmware up and running standalone by tomorrow. Thanks and Regards, Jim -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email .....listservKILLspam.....mitvma.mit.edu with SET PICList DIGEST in the body

> When I run my code using the ICD, all works as planned. However, as > soon as I disable the ICD executive code so that it runs in stand > alone mode, it doesn't work. I don't know much about the ICD (I use the ICE-2000), but here are a few things to think about: 1 - What does your external circuit do with the ICD lines when the ICD is not connected? I assume the ICD connects to MCLR and LVP, both of which could cause trouble if not driven correctly. 2 - Does the oscillator oscillate? 3 - Check for uninitialized variables. One way to check for this is to insert code right in the beginning that sets all RAM to 0. If it works then, you've got an uninitialized variable problem. 4 - What are you doing for good bank and page discipline? Errors here can show up when code is moved to a different location, such as when the ICD kernel is removed. 5 - I all else fails, put a dumb loop in the beginning just to wiggle an I/O pin. If the pin wiggles, then at least you know the processor is starting up and running at all. Then you can progress the wiggle test thru your code to see where it gets stuck. 6 - If this is a commercial product, it doesn't take a lot of wasted hours to pay for an ICE. > If so, please reply to me ASAP at EraseMEjpaulspam_OUTTakeThisOuTappliedmems.com. No. This is a discussion list. You can see answers to your posts here just like everyone else. Many people here won't want to waste time writing an answer that only one person will read. > I have to get my firmware up and running standalone by tomorrow. Not our problem. This kind of "Treat me special because I'm so important" arrogance is a dumb move when you're asking 2000 people for a favor. ***************************************************************** Embed Inc, embedded system specialists in Littleton Massachusetts (978) 742-9014, http://www.embedinc.com -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email listservspam_OUTmitvma.mit.edu with SET PICList DIGEST in the body

At 03:12 PM 5/15/03 +0500, you wrote: > However, as > soon as I disable the ICD executive code so that it runs in stand alone > mode, it doesn't work. I've single stepped through it in ICD mode, and > see nothing that would cause it to stop working. So my geuss is I'm > missing something when turning off the ICD mode. What I do to disable > it is to uncheck the checkbox in the ICD options dialog near the bottom > that says 'Enable Debug Mode'. When I do this, and reprogram the chip, > it should run in stand alone mode, correct? > > Does anyone have any ideas or clues as to what I'm doing wrong? > > If so, please reply to me ASAP at @spam@jpaulKILLspamappliedmems.com. With the ICD2, it works for me exactly like you describe. To get the target code to run, the connector to the target board from the ICD2 must be removed as it asserts the reset line and holds the target chip in reset. Tom M. -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email KILLspamlistservKILLspammitvma.mit.edu with SET PICList DIGEST in the body

The same with ICD1. Just unplug the connector from ICD module. Regards, Samo --- Tom Messenger <RemoveMEkristTakeThisOuTTHEGRID.NET> wrote: {Quote hidden}> At 03:12 PM 5/15/03 +0500, you wrote: > > > However, as > > soon as I disable the ICD executive code so that > it runs in stand alone > > mode, it doesn't work. I've single stepped > through it in ICD mode, and > > see nothing that would cause it to stop working. > So my geuss is I'm > > missing something when turning off the ICD mode. > What I do to disable > > it is to uncheck the checkbox in the ICD options > dialog near the bottom > > that says 'Enable Debug Mode'. When I do this, > and reprogram the chip, > > it should run in stand alone mode, correct? > > > > Does anyone have any ideas or clues as to what > I'm doing wrong? > > > > If so, please reply to me ASAP at > spamBeGonejpaulspamBeGoneappliedmems.com. > > > With the ICD2, it works for me exactly like you > describe. > > To get the target code to run, the connector to the > target board from the > ICD2 must be removed as it asserts the reset line > and holds the target chip > in reset. > > Tom M. > > -- > http://www.piclist.com#nomail Going offline? Don't > AutoReply us! > email TakeThisOuTlistservEraseMEspam_OUTmitvma.mit.edu with SET PICList > DIGEST in the body __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com -- http://www.piclist.com#nomail Going offline? Don't AutoReply us! email RemoveMElistservTakeThisOuTmitvma.mit.edu with SET PICList DIGEST in the body

ntlolgies if you realise this but if you have disabled debug mode you still have to hit "Run" to get the ICD to control the MCLR. Otherwise just disconnect the ICD from the board. DAN {Quote hidden}> > From: "Paul James E." <jamespEraseME.....INTERTEX.NET> > Date: 2003/05/15 Thu AM 10:12:47 GMT > To: EraseMEPICLISTMITVMA.MIT.EDU > Subject: [PIC]: ICD Question > > All, > > I have developed some code for an in house test system using the 16F877 > and the ICD1 system from Microchip. > > When I run my code using the ICD, all works as planned. However, as > soon as I disable the ICD executive code so that it runs in stand alone > mode, it doesn't work. I've single stepped through it in ICD mode, and > see nothing that would cause it to stop working. So my geuss is I'm > missing something when turning off the ICD mode. What I do to disable > it is to uncheck the checkbox in the ICD options dialog near the bottom > that says 'Enable Debug Mode'. When I do this, and reprogram the chip, > it should run in stand alone mode, correct? > > Does anyone have any ideas or clues as to what I'm doing wrong? > > If so, please reply to me ASAP at RemoveMEjpaulEraseMEEraseMEappliedmems.com. > > I have to get my firmware up and running standalone by tomorrow. > > > Thanks and Regards, > > Jim > > -- > http://www.piclist.com#nomail Going offline? Don't AutoReply us! > email RemoveMElistservspam_OUTKILLspammitvma.mit.edu with SET PICList DIGEST in the body > -- http://www.piclist.com hint: To leave the PICList RemoveMEpiclist-unsubscribe-requestTakeThisOuTspammitvma.mit.edu>