Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - codematic

#1
Greetings,

Is getting 0x50 back from the X2 Bit setting valid ?

According to AN461 only bit 7 is valid, or rather is set for 12/6 clock mode. But i am seeing this returned as x50...

Any one have a clue if this matters ?

Thanks,
Lenny

TX -->  ":020000050003F6"
RX <--- ":020000050003F650."

**  READ : CLOCKBIT = 0x50

#2
Thanks,

Just as a point of disclaimer, i see this issue with your software utility as well as my own perl script that implements the protocol. That is how i know the "R"'s are being sent.

So i think your utility is not the issue, but rather my use of these CPU's.

Looking at my layout, i can see that 2.7 is tied high, but 2.6 is being used as a clock bit for another device. That could be the cause of the issue.

Is it your experience that when a device is sending "R" for programming that it can be recovered then. (and hopefully via ISP...) ?

Thanks For your help,
-Lenny
#3
Greetings,

I have had a few of my MCU's "die" in this described manner, and am a little confused as to how this can happen...

I can communicate with the bootloader, read the settings, but when i attempt to actually flash the device it is failing.  (Which means that it is sending back and "R" rather than a "." character when the programming line is sent).

Does anyone know A) How this can Happen, or Why  B) How do i recover ?

Thanks, !
Codematic

PS : Your flashmagic utility kicks major butt. :)



Post Edited (05-26-04 03:58)