??? 08/15/05 14:23 Modified: 08/15/05 14:27 Read: times |
#99438 - and now we know why Responding to: ???'s previous message |
From my previous post earlier on, sorry for not mentioning, I am doing multi processor communication using Tx/Rx, Tx2/Rx2.
This will be followed by a software reset using ((void (code *)(void)) 0) (); // Software Reset Your chip has an internal watchdog, using that (letting it time out) gives a much safer reset. My problem is during the Copying of the Flash from (0x1800) to (0x0000), it works only if I copy in the decrementing order (from 0x2780, 0x2700, 0x2680, ... and so on... 0x1800). If I do the copying in the incrementing order (from 0x1800, 0x1880, 0x1900, .... 0x2780), it only manage to copy to location (0x100 -> 0x200), and then the whole thing hang. We all know the problem of not seeing the forrest for the trees and I think that is it. Do post both versions of the code and someone probably will spot the problem. Erik |
Topic | Author | Date |
Strange problem IAP for whole chip | 01/01/70 00:00 | |
Questions please | 01/01/70 00:00 | |
Nobody knows? | 01/01/70 00:00 | |
why | 01/01/70 00:00 | |
For IAP? | 01/01/70 00:00 | |
Which is exactly what FlashMagic is inte | 01/01/70 00:00 | |
and now we know why | 01/01/70 00:00 | |
Get a PC | 01/01/70 00:00 | |
Enclose PCB in a box | 01/01/70 00:00 | |
I understand | 01/01/70 00:00 | |
Process make sense | 01/01/70 00:00 | |
Thank god for the response | 01/01/70 00:00 | |
Maybe the libraries in causing it ??? | 01/01/70 00:00 | |
the problem with absolutes | 01/01/70 00:00 | |
AT89C51RC2 with 128 bytes per page | 01/01/70 00:00 | |
there is no such thing as a byte write, | 01/01/70 00:00 | |
byte write | 01/01/70 00:00 | |
No byte write | 01/01/70 00:00 | |
what was the problem? | 01/01/70 00:00 | |
Problem was ... | 01/01/70 00:00 | |
OK, now face problems in Variables | 01/01/70 00:00 | |
variables used in my remote update | 01/01/70 00:00 | |
Ok, Solved | 01/01/70 00:00 | |
Try this![]() | 01/01/70 00:00 |