|
Samperiau wrote: > It is not very clear from the docs. I have downloaded the latest > "Pink book" and it seems to show that the normal HC711 can be > protected. It simply erases the EEPROM, which is ok with me. The > 'S' version seems to have additional protection where the chip > becomes unusable. It refers to the (wrongly numbered) application > note. > > Still don't understand how issuing the command MS 103f 05 CLEARS > the NOSEC bit (bit 3)when it is set in $05 (%00001001). Anyone > from Motorola can shed any light on this? I went through the same thing a while back. Even though it says in the pink book that you can enable the security on the E9 and E20 flavours of the HC11, it is a factory mask option only. In other words, OTP chips do not have this feature enabled. If you order mask programmed chips from the factory, you can specify that the security feature is enabled. You can also order 68S711E9 chips, which are OTP's and can be secured. Hope this helps. I have attached my correspondence with a Motorla rep wrt this issue. Then, at least, you can get it "from the horses mouth": ------------------------------------------------------------------------------------------ Darrell: I think I finally got the skinny from the factory. The 'S711E9 is the only device that has the enhanced security feature. The 'E20 and 'E32 do NOT have security enabled unless you order a special part that enables this feature. The part number would be specific your application since it is only available on ROM devices. You would need to order the MC68HC11E20 and then send your final code to Motorola for masking. The only device that has security available is the MC68SEC811E2. So, if you need security you will need to talk to your sales rep. to get this straightened out. Once again, if you order standard parts that look like MC68HC711E20... you ordered a part that has NO security. Sorry about the confusion. Regards, John Honnold "Darrell N." wrote: > > Just a note to thank you for your prompt reply. However, I'm still > confused. > > In app note EB422, it clearly states that the 'E20 and 'E32 have an > enhanced bootstrap mode which does not allow access to the EPROM > in the device if the NOSEC bit is cleared in the config register. > The bootloader does a blank check on the EPROM when the device is put > into bootstrap mode, and if the bootstrap loader finds any address > that is not blank, it will go into an endless loop and prevent any > access to the chip via bootstrap mode, essentially rendering bootstrap > mode inoperative. It also states that these two devices have PCBug11 > Talkers built into the boot code. > > Now, this is what is stated in official Motorola documentation, > but you say this is not implemented. Which case is correct? > > I have already purchased a bunch of 'E20's based on this information, > because the S'E9's are vaporware at this time. I'm hoping I've not > wasted a lot of time and money... > > Darrell Norquay > Datalog Technology Inc. Darrell Norquay Datalog Technology Inc. Voice: (403) 243-2220 Fax: (403) 243-2872 Email: Web: www.datalog.ab.ca |