Searching \ for 'IDs not blank?' in subject line. ()
Make payments with PayPal - it's fast, free and secure! Help us get a faster server
FAQ page: techref.massmind.org/techref/index.htm?key=ids+not+blank
Search entire site for: 'IDs not blank?'.

Truncated match.
PICList Thread
'IDs not blank?'
1999\03\29@200412 by PJH

flavicon
face
Hi,

I've got a 16C57C which I'm
programming with PICSTART+ as a
16C57.
(PICSTART doesn't have a "C" option
in the 57 series as the 16C57C
seems too new. I can't see any
differences in the data sheet
specs?)

OK, I've erased it with *really*
thoroughly - barber's UV sterilser
which
zaps all other windowed chips I've
ever seen in less than 5 min. This
one's
had a good hour.

But still PICSTART comes back with
the message ... I'm wondering  how
identical the 16C57C is and whether
there's an update from Microchip?

"Device NOT blank : IDs"

My config settings are :-
PIC16C57
OSC ... XT
WDT ... OFF
CP  ... OFF

Any thoughts on what would seem to
be the problem here?

Thanks for advice - PJH

1999\03\29@211113 by Steve Ridley

flavicon
face
I don't have personal experience with this problem but I recall it being
discussed on the list recently. There is a difference between 57A or B
devices and the 57C devices. I think the difference has to do with the
programming algorithm. The solution was to download a new driver for the
PICSTART+ programmer. The driver code is got from the Microchip web page.
There should be some up to date information about the 57C on this web page
somewhere.

Steve

{Original Message removed}

1999\03\30@032036 by PJH

flavicon
face
Hey, thanks for the tip Steve,
There's an updated MPLAB in u-chip's "Development Tools" section which I'll
download tomorrow morning - 8.5MB.
The 16C57C is mentioned so that must be it.

Regards - PJH

Steve Ridley wrote:

> I don't have personal experience with this problem but I recall it being
> discussed on the list recently. There is a difference between 57A or B
> devices and the 57C devices. I think the difference has to do with the
> programming algorithm. The solution was to download a new driver for the
> PICSTART+ programmer. The driver code is got from the Microchip web page.
> There should be some up to date information about the 57C on this web page
> somewhere.
>
>


'IDs not blank?'
1999\04\01@204650 by PJH
flavicon
face
Hi,

Ah, look, I'm sorry to bug everybody again with this problem as I know it's been
raised before, but .... well, it's like this.
I've got a couple of hundred bucks worth of windowed PIC 16C57C chips which I
can't programme with PICSTART+
'cause there's something new (I think!) with the chip. As I said before, I get
"NOT BLANK: Device IDs"

OK, following Steve Ridley's helpful advice I did the following :
1/ Downloaded & installed MPLAB4.00, replacing my old 3.40.
Result : No change. The 16C57C's not mentioned in the new 16c5xx.inc file.
That's a worry.

2/ Sifted thru u-chip's "Development Tools" files, FAQs etc for anything to do
with the 16C57C.
Result: Can't find anything relevant to my problem

3/Downloaded the latest16C5X data sheet + revisions.
Result: Can't find anything different about the 57C, except it uses 0.7 micron
process technologhy i/s/o 1.2 for the 57

4/ Emailed "Technical Support" at u-chip
Result: No answer so far - but then it's Easter

5/ Downloaded some PICLIST archives, 'cause Steve said the matter's been raised
before.
Result: I only got January's lot 'cause the server said I'd exceeded my quota -
ie all 5MB and I've gotta wait 8 hours.
Man, this thing's teaching PATIENCE as a virtue! Anyway, with 5MB, unindexed,
it'll probably take till Xmas to plough thru'em all. And that's only for
January.

Basically, it looks like I'm stumped for Easter. Unless somebody's got the
answer out there?

So, what exactly do I need to do to programme these 16C57Cs? Some sort of new
driver or what? Any specific file name?

Any help\advice much appreciated!!

Regards & thnax in advance - PJH

PS: If anyone *does* come up with the answer, I'll post a neat routine for a 3
digit ASCII counter. Sort of an electronic
odometer using an HD44780 - in fact that's what it was for. Somebody asked about
something like that I think?


PJH wrote:

{Quote hidden}

1999\04\01@205720 by Jason Van Dellen

flavicon
face
There's a Firmware upgrade for the PICSTART for the 57C and 54C devices.  I
don't know if you've done that yet.  Hope it helps.

www.microchip.com/10/Tools/PICmicro/Program/picstart/psfw200/index.ht
m

Jason

{Original Message removed}

1999\04\01@212845 by Reginald Neale

flavicon
face
PJH asked:

>I've got a couple of hundred bucks worth of windowed PIC 16C57C chips which I
>can't programme with PICSTART+
>'cause there's something new (I think!) with the chip. As I said before, I get
>"NOT BLANK: Device IDs"

Did you try ignoring the error message? I think I've run into this before
with 16C54's, and it was some kind of artifact. If you can afford to risk
wasting a chip, go ahead with the programming and check the functionality
in circuit.

Reg Neale

1999\04\02@110211 by J Nagy

flavicon
face
>PJH asked:
>
>>I've got a couple of hundred bucks worth of windowed PIC 16C57C chips which I
>>can't programme with PICSTART+
>>'cause there's something new (I think!) with the chip. As I said before,
>>I get
>>"NOT BLANK: Device IDs"
>
>Did you try ignoring the error message? I think I've run into this before
>with 16C54's, and it was some kind of artifact. If you can afford to risk
>wasting a chip, go ahead with the programming and check the functionality
>in circuit.
>
>Reg Neale

       Have you used these once? If you have, are you aware that the ID
locs and the config bits seem to take at least 3x longer than the data area
to erase. Some testing I did once on some '508s showed ~5mins to erase all
the data words while the config and IDs take ~20mins (using a dataraseII).

       Jim Nagy
       Elm Electronics
 ICs for Experimenters
http://www.elmelectronics.com/

1999\04\02@155956 by PJH

flavicon
face
Hey thnaks, Jason.

I've downloaded the file & it seems to be just what's required. Dang, it was
right in front of me the whole time.

Seems that you need to reprogramme the u-controller in the PICSTART+, so there
won't be much I can do till after the Easter break anyway, as I'll have to get
new chip.

That DID help!

Regards - PJH

Jason Van Dellen wrote:

> There's a Firmware upgrade for the PICSTART for the 57C and 54C devices.  I
> don't know if you've done that yet.  Hope it helps.
>
> www.microchip.com/10/Tools/PICmicro/Program/picstart/psfw200/index.ht
> m
>
> Jason
>

PS: Did I say something about putting up a routine as quid pro quo for the
answer to this?
Well, here it is. It's probably been done 10,000 times before but when *I* had
to crack it it, it nearly drove me crazy.

;**********************************************************************
;VERSION  : #A .. uses 16C57 to step thru messages
;DATE     : June 30, 1998
PURPOSE   : To perform an event count for an ASCII\LCD readout
;AUTHOR   : P.J. Hynes
;RATING   : Copyright (c) 1999 to Elektromart Pty. Ltd.
;COMMENTS : Rewritten from LCD55, from June 30, 1998.
;           We begin by stepping thru -100 to + 100 on the HD44780 LCD.
;           Compiles and simulates OK within MPLAB environment.
;           Hardware tested OK
;
;The UPDATE routine tests b4=1 of messnum to see if the display count
;should be updated. If so, each ASCII character is tested to see if it's
;9. If it is, that character is incremented and the procedure then returns
;to the main programme. The updated digits are stored in digit1, digit2
;& digit3. When 999 is reached, the display count resets to 000. The
;contents of digit1, digit2 & digit3 can then be retrieved for despatch
;to an LCD.
;**********************************************************************
update   btfss    messnum,4   ;Increment counter? Is b4=1?
        goto     goback      ;No  - go back to main routine.
        movf     digit1,w    ;Yes - retrieve 1st digit.
        xorlw    0x039       ;Test if it has reached 9d
        btfss    STATUS,2    ;Is Z=1? Is digit1=39h?
          goto   inc1        ;No  - inc the LSD
        movlw    0x030       ;Yes - reset the digit.
        movwf    digit1
        movf     digit2,w    ;Retrieve 2nd digit.
        xorlw    0x039       ;Test if it has reached 9d
        btfss    STATUS,2    ;Is Z=1?Is digit1=39h?
          goto   inc2        ;No  - inc the middle digit
        movlw    0x030       ;Yes -
        movwf    digit2
        movf     digit3,w    ;Retrieve 3rd digit.
        xorlw    0x039       ;Test if it has reached 9d
        btfss    STATUS,2    ;Is Z=0?Is digit1=39h?
          goto   inc3        ;No  - inc the MSD
        movlw    0x030       ;Yes - reset the display to 000 ..
        movwf    digit1
        movwf    digit2
        movwf    digit3
        goto     goback      ;.. and return.
inc1     incf     digit1,1    ;Update each digit as appropriate ..
        goto     goback
inc2     incf     digit2,1
        goto     goback
inc3     incf     digit3,1
goback   nop                  ;.. and return.
        retlw    0x00

1999\04\02@161210 by Jason Van Dellen

flavicon
face
Your welcome.

Glad to hear  :)

Jason
-----Original Message-----
From: PJH <spam_OUTelekTakeThisOuTspamNETSTRA.COM.AU>
To: .....PICLISTKILLspamspam@spam@MITVMA.MIT.EDU <PICLISTspamKILLspamMITVMA.MIT.EDU>
Date: Friday, April 02, 1999 1:52 PM
Subject: Re: IDs not blank?


>Hey thnaks, Jason.
>
>I've downloaded the file & it seems to be just what's required. Dang, it
was
>right in front of me the whole time.
>
>Seems that you need to reprogramme the u-controller in the PICSTART+, so
there
>won't be much I can do till after the Easter break anyway, as I'll have to
get
{Quote hidden}

www.microchip.com/10/Tools/PICmicro/Program/picstart/psfw200/index.ht
>> m
>>
>> Jason
>>
>
>PS: Did I say something about putting up a routine as quid pro quo for the
>answer to this?
>Well, here it is. It's probably been done 10,000 times before but when *I*
had
{Quote hidden}

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