Yahoo Groups archive

68300

Index last updated: 2026-04-29 00:01 UTC

Thread

Identifying 68F375 revision number...?

Identifying 68F375 revision number...?

2002-09-17 by Jeff Andle

Apparently the flash programming algorithm is mask-revision dependent for the 'F375.

My parts have the full part number, MC68F375BGMZP33
and two other lines

8J28H 

and QEAL0107C

Anything there which would readily identify a mask rev?

Thanks.


[Non-text portions of this message have been removed]

RE: [68300] Identifying 68F375 revision number...?

2002-09-17 by Bob McMillan

Jeff,

After searching everything available to me I believe you should submit this
question directly to the Motorola Help line.  This is one of the issues that
they should be able to get you an answer for a lot easier and quicker than
anyone on the list.

That said based on the Core part number this looks to me like either a B or
G rev, and I don't think B That is an option.  BTW the completeness of your
question would have made this easy to find if the information was out there.

Regards,
Robert (Bob) McMillan
Technical Solutions Manager
Future Electronics, Calgary
Phone: (403)-219-3443 OR (888)-285-3443
Cell: (403)-606-6256
Fax: (403)-291-7054
email: bob.mcmillan@...
Website: www.futureelectronics.com

******   Check out the Future Engineering Resource Center website:
www.futureerc.com 
60 day loan on development tools, industry newsletters on new technology,
app notes,etc
Show quoted textHide quoted text
-----Original Message-----
From: Jeff Andle [mailto:andle@...]
Sent: Tuesday, September 17, 2002 5:51 AM
To: 68300@yahoogroups.com
Subject: [68300] Identifying 68F375 revision number...?


Apparently the flash programming algorithm is mask-revision dependent for
the 'F375.

My parts have the full part number, MC68F375BGMZP33
and two other lines

8J28H 

and QEAL0107C

Anything there which would readily identify a mask rev?

Thanks.


[Non-text portions of this message have been removed]



---------------------------------------------------
To unsubscribe from this group, send an email to:
68300-unsubscribe@yahoogroups.com

To learn more about Motorola Microcontrollers, please visit
http://www.motorola.com/mcu

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

Re: [68300] Identifying 68F375 revision number...?

2002-09-19 by Charles Melear

Jeff,

The mask number is 8J28H.  It is generally the line right unter the part number.

Charlie
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Jeff Andle 
  To: 68300@yahoogroups.com 
  Sent: Tuesday, September 17, 2002 6:50 AM
  Subject: [68300] Identifying 68F375 revision number...?


  Apparently the flash programming algorithm is mask-revision dependent for the 'F375.

  My parts have the full part number, MC68F375BGMZP33
  and two other lines

  8J28H 

  and QEAL0107C

  Anything there which would readily identify a mask rev?

  Thanks.


  [Non-text portions of this message have been removed]


        Yahoo! Groups Sponsor 
              ADVERTISEMENT
             
       
       

  ---------------------------------------------------
  To unsubscribe from this group, send an email to:
  68300-unsubscribe@yahoogroups.com

  To learn more about Motorola Microcontrollers, please visit
  http://www.motorola.com/mcu



  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 



[Non-text portions of this message have been removed]

Re: [68300] Identifying 68F375 revision number...?

2002-09-19 by Charles Melear

Hello everyone,

With regard to rev and mask numbers, the only one that really means anything
is the mask number.

REgards,

Charlie
----- Original Message -----
From: "Bob McMillan" <Bob.McMillan@...>
To: <68300@yahoogroups.com>
Sent: Tuesday, September 17, 2002 10:56 AM
Subject: RE: [68300] Identifying 68F375 revision number...?


> Jeff,
>
> After searching everything available to me I believe you should submit
this
> question directly to the Motorola Help line.  This is one of the issues
that
> they should be able to get you an answer for a lot easier and quicker than
> anyone on the list.
>
> That said based on the Core part number this looks to me like either a B
or
> G rev, and I don't think B That is an option.  BTW the completeness of
your
> question would have made this easy to find if the information was out
there.
Show quoted textHide quoted text
>
> Regards,
> Robert (Bob) McMillan
> Technical Solutions Manager
> Future Electronics, Calgary
> Phone: (403)-219-3443 OR (888)-285-3443
> Cell: (403)-606-6256
> Fax: (403)-291-7054
> email: bob.mcmillan@...
> Website: www.futureelectronics.com
>
> ******   Check out the Future Engineering Resource Center website:
> www.futureerc.com
> 60 day loan on development tools, industry newsletters on new technology,
> app notes,etc
>
>
> -----Original Message-----
> From: Jeff Andle [mailto:andle@...]
> Sent: Tuesday, September 17, 2002 5:51 AM
> To: 68300@yahoogroups.com
> Subject: [68300] Identifying 68F375 revision number...?
>
>
> Apparently the flash programming algorithm is mask-revision dependent for
> the 'F375.
>
> My parts have the full part number, MC68F375BGMZP33
> and two other lines
>
> 8J28H
>
> and QEAL0107C
>
> Anything there which would readily identify a mask rev?
>
> Thanks.
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ---------------------------------------------------
> To unsubscribe from this group, send an email to:
> 68300-unsubscribe@yahoogroups.com
>
> To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
> ---------------------------------------------------
> To unsubscribe from this group, send an email to:
> 68300-unsubscribe@yahoogroups.com
>
> To learn more about Motorola Microcontrollers, please visit
> http://www.motorola.com/mcu
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.