Searching \ for 'Quickest way to get an ICD-2 to program a PIC' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: www.piclist.com/techref/microchip/devprogs.htm?key=icd
Search entire site for: 'Quickest way to get an ICD-2 to program a PIC'.

Truncated match.
PICList Thread
'Quickest way to get an ICD-2 to program a PIC'
2008\07\30@092824 by Matthew Rhys-Roberts

flavicon
face
I'm looking for the most direct way of blowing established PIC code (I
guess it's the .HEX file) into any particular PIC, using a straight
WinPC and an ICD-2 programmer, so that the operator of this procedure
doesn't have to worry about opening projects, compiling etc.

All suggestions gratefully appreciated.

Matt Rhys-Roberts

2008\07\30@094045 by Artem Zezyulinskiy

flavicon
face
Hi, Matt.

In MPLAB IDE you can _Import_ a hex., cof, or cod. files from File Menu.
And directly programm the PIC with ICD-2

Artem.

Matthew Rhys-Roberts a écrit :
> I'm looking for the most direct way of blowing established PIC code (I
> guess it's the .HEX file) into any particular PIC, using a straight
> WinPC and an ICD-2 programmer, so that the operator of this procedure
> doesn't have to worry about opening projects, compiling etc.
>
> All suggestions gratefully appreciated.
>
> Matt Rhys-Roberts
>  

2008\07\30@102338 by Mauricio Giovagnini

flavicon
face
Artem Zezyulinskiy escribió:
> Hi, Matt.
>
> In MPLAB IDE you can _Import_ a hex., cof, or cod. files from File Menu.
> And directly programm the PIC with ICD-2
>

That's true but the user will also have to select the device
in the Configure menu, under the Select Device option.

An HEX file has no information about the device to which the
code belongs.


--
------------------------------
Mauricio Giovagnini (Maunix)
http://www.maunix.com.ar
Cordoba, Arg.
LinkedIn Profile: http://www.linkedin.com/in/mgiovagnini

2008\07\30@104536 by Harold Hallikainen

face
flavicon
face

> I'm looking for the most direct way of blowing established PIC code (I
> guess it's the .HEX file) into any particular PIC, using a straight
> WinPC and an ICD-2 programmer, so that the operator of this procedure
> doesn't have to worry about opening projects, compiling etc.
>
> All suggestions gratefully appreciated.
>
> Matt Rhys-Roberts
> --

On the older Promates, I used to have DOS batch files that would send
commands to the Promate. I had one batch file for each product and a menu
to select the batch files. I don't think there's a command line interface
to the ICD-2, though. That would be kind of nice.

Having used the Promate, Promate II, and now the PM3 for production, the
SD card on the PM3 is nice. The programmer stands alone in production and
the user selects the product from the menu on the PM3. The "environment"
is read from the SD card and the devices programmed. All the products fit
on a single SD card that is always in the programmer.

So... that does not answer the ICD-2 question. I also don't like
production having to dig through MPLAB just to program a chip.

Harold


--
FCC Rules Updated Daily at http://www.hallikainen.com - Advertising
opportunities available!

2008\07\30@104538 by Artem Zezyulinskiy

flavicon
face
Exactly, I forgot this :)

Mauricio Giovagnini a écrit :
> Artem Zezyulinskiy escribió:
>  
>> Hi, Matt.
>>
>> In MPLAB IDE you can _Import_ a hex., cof, or cod. files from File Menu.
>> And directly programm the PIC with ICD-2
>>
>>    
>
> That's true but the user will also have to select the device
> in the Configure menu, under the Select Device option.
>
> An HEX file has no information about the device to which the
> code belongs.
>
>
>  

--
Artem ZEZYULINSKIY
SEDATELEC, Chemin des Mûriers
Irigny, 69540, FRANCE
Tel : +33 [0] 472 663 326

2008\07\30@104948 by Tamas Rudnai

face picon face
That's what I found, seems to be ok for scripting, however, I have not
tested it yet:

ProgICD2 : Standalone PIC programmer for Microchip's ICD2
http://www.edaboard.com/ftopic267847.html


Also Microchip has something for industrial users:

MPLAB Production Test Interface
http://forum.microchip.com/tm.aspx?m=323781

Tamas



On Wed, Jul 30, 2008 at 3:27 PM, Mauricio Giovagnini <
spam_OUTmaugiovagniniTakeThisOuTspamyahoo.com.ar> wrote:

{Quote hidden}

>

2008\07\30@105405 by Matthew Rhys-Roberts

flavicon
face
Thanks, that looks pretty simple!

Matt

2008\07\30@111448 by Funny NYPD

picon face
Why not use the PICkit 2 programmer to go function. Just push a button, the hex file is loaded to a chip. No PC, or any set up required.

Check with my web site:
www.auelectronics.com/System-PICkit2.htm
And here is the tutorial:
http://www.auelectronics.com/UserManual-PICKit2ProgrammerToGo.htm

There are two you-tube video showing how "easy" it would be.

Funny N.
Au Group Electronics, New Bedford, MA, http://www.AuElectronics.com



{Original Message removed}

2008\07\30@114338 by Matthew Rhys-Roberts

flavicon
face
Thanks for this and all other replies.
Matt    :)
> Why not use the PICkit 2 programmer to go function. Just push a button, the hex file is loaded to a chip. No PC, or any set up required.
>
> Check with my web site:
> www.auelectronics.com/System-PICkit2.htm
> And here is the tutorial:
> http://www.auelectronics.com/UserManual-PICKit2ProgrammerToGo.htm
>
> There are two you-tube video showing how "easy" it would be.
>
>  Funny N.
> Au Group Electronics, New Bedford, MA, http://www.AuElectronics.com
>  

2008\07\30@141317 by Vic Fraenckel

picon face
Matthew Rhys-Roberts wrote:
> I'm looking for the most direct way of blowing established PIC code (I
> guess it's the .HEX file) into any particular PIC, using a straight
> WinPC and an ICD-2 programmer, so that the operator of this procedure
> doesn't have to worry about opening projects, compiling etc.
>
> All suggestions gratefully appreciated.
>
> Matt Rhys-Roberts
>  
Matthew,

I suggest that your post should have had the [PIC] tag so it could be
routed properly.

Vic

--

*____________________________________________________________________________________________*

*Victor Fraenckel
KC2GUI
windswaytoo ATSIGN gmail DOT com**

*


'Quickest way to get an ICD-2 to program a PIC'
2008\08\19@094027 by Dario Greggio
face picon face
Mauricio Giovagnini wrote:

>
> That's true but the user will also have to select the device
> in the Configure menu, under the Select Device option.
>
> An HEX file has no information about the device to which the
> code belongs.

Hmmm, if it included DEVID bytes, it possibly could...

--
Ciao, Dario

2008\08\19@162642 by Barry Gershenfeld

face picon face
At 03:40 PM 8/19/08 +0200, you wrote:
>Mauricio Giovagnini wrote:
> > That's true but the user will also have to select the device
> > in the Configure menu, under the Select Device option.
> >
> > An HEX file has no information about the device to which the
> > code belongs.
>
>Hmmm, if it included DEVID bytes, it possibly could...
>--
>Ciao, Dario

Oddly enough, my hex files do have this.  It's obviously a result of using
the CCS compiler, but it's interesting to note that MPLAB never gets
upset.  So you could put that info in by hand and it could tell your
scripts what to do...

As an example, here are the last two lines of a hex file I'm working on.

:00000001FF
;PIC12F675

Barry

2008\08\20@033648 by Wouter van Ooijen

face picon face
> As an example, here are the last two lines of a hex file I'm working on.
>
> :00000001FF
> ;PIC12F675

Is that an official format, documented somewhere?


--

Wouter van Ooijen

-- -------------------------------------------
Van Ooijen Technische Informatica: http://www.voti.nl
consultancy, development, PICmicro products
docent Hogeschool van Utrecht: http://www.voti.nl/hvu

2008\08\20@041851 by Tamas Rudnai

face picon face
I guess it is just a hack as the last line in this example is after the
end-of-record marker.

Tamas


On Wed, Aug 20, 2008 at 8:35 AM, Wouter van Ooijen <.....wouterKILLspamspam@spam@voti.nl> wrote:

{Quote hidden}

> -

2008\08\21@051059 by Dario Greggio

face picon face
Barry Gershenfeld wrote:

> Oddly enough, my hex files do have this.  It's obviously a result of using
>[...]

> As an example, here are the last two lines of a hex file I'm working on.
>
> :00000001FF
> ;PIC12F675

Hmmm, nice one Barry!
While the first is the "standard" end-of-file for HEX files, the comment
that follows is a good one which could indeed help.

(I never used CCS)
--
Ciao, Dario

More... (looser matching)
- Last day of these posts
- In 2008 , 2009 only
- Today
- New search...