Re: HC08 monitor mode, security problem

>> We use the AZ60. I checked, programming via monitor mode is the same for
>> the
>> AZ60 and the AZ60A.
>
> If the programmer treats them as the same device, then the routine that is
> loaded into the AZ60's RAM to do the mass erase must detect if it's
> running
> on a AZ60 or a AZ60A because looking at the datasheets/application notes
> shows that various registers such as the FL1CR/FL2CR are located at
> different
> addresses on the 2 variants.

You are right, there are some differences in the area of mass erasing. But
what I ment with programming via monitor mode above was using the basic
commands suchs as Read, Write, IRead, IWrite, ReadSP, Run.

> My only other suggestions are:
>
> 1) What are you actually getting back from the EPROM area when you try to
> read it ? On the variants that I use, you get $AD back when you fail
> security.

That's right, I read $AD's from de FLASH/EPROM area.

> 2) You could always write a little mass erase routine of your own in
> assembly
> language using the algorithm in the datasheet and load/execute that from
> RAM
> if your programmer will let you do that.

> 3) Does your programmer do a verify pass on the mass erase/programming
> code it's loaded into the AZ60's RAM before it has the monitor execute it
> ?
> I'm wondering if this code is getting corrupted during the loading
> process.

I just got things working (a bit) ! I used P&E's Prog08sz to mass erase the
MCU. Appearantly it does this without any warnings or errors. What I've been
trying to do until now is to bypass security after mass erase, which does
not seem to work. However, after loading the flash-programming routines in
RAM (after mass erasing), programming of FLASH seems to be possible, even
without bypassing the security! I don't know if that is the regular way to
do it (must have been misreading a lot of things then ...) but anyway, I'm
not stuck anymore !

> Other than that, are you sure that you haven't just got a faulty batch ?

Can't really tell ... I have tested some 15 or so MCU's from the same batch,
they all respond the same however.

Thanks for your help !

Regards,
Roy


.

Relevant Pages

  • Re: On Error Resume Next
    ... > I've gone from being a total newbie, to an OK beginner programmer but ... If you want error handling, it must go in each routine where you want it. ... doesn't drop into the error handler. ...
    (microsoft.public.word.vba.beginners)
  • Re: First steps on overloading
    ... the programmer to be sure which procedure is to be invoked. ... Use the types of data1 and data2 and the type of result. ... Bear in mind I'm not so much trying to uniquely identify a routine ...
    (comp.lang.misc)
  • Re: Which do you prefer?
    ... 'routine X seems like the logical place to put this instead ... ' (insert dire consequences). ... Robin S. ... missing then you're a sloppy programmer. ...
    (microsoft.public.dotnet.languages.vb)
  • Software bloat (was Re: Using Final Cut Pro X)
    ... non-professionals can use. ... learning how to program with limited memory and slow ... I'm a former Apple II programmer (including assembly ... The first embedded processor I worked on in my job had 192 bytes of RAM ...
    (comp.sys.mac.apps)
  • Re: Kader have bought Sander Kan!
    ... dual-channel memory or not? ... motherboard, and HP specifies matching pairs of RAM chips. ... Manager reports 3,144,104KB total RAM. ... Well as an ex-mainframe systems programmer that moved on to UNIX admin esp ...
    (uk.rec.models.rail)