| ??? 05/02/07 14:46 Read: times |
#138474 - Hoorah for Winbonds Responding to: ???'s previous message |
Sorry Erik, couldn't resist it.
I only use Winbond 516s (apart from an ancient Siemens in my ICE) - never had any sort of problem with auxram - EVER. I never write protect it, once writing has been enabled during init, however. I also note that my (10-year-old) code movs CHPCON to a, setb ACC.4, and movs it back again. I'm trying to remember why I did that ;-) I note you omit the suggested 'mov CHPENR,#0' - which disables further writes to CHPCON after the enabling/disabling write. Could something be corrupting CHPENR? - that's why they have that 2 x special byte write to enable it, after all. They must feel it is vulnerable to something. As Jan says - What are the symptoms? Dave |
| Topic | Author | Date |
| calling Winbond specialists | 01/01/70 00:00 | |
| what datasheet do you have? | 01/01/70 00:00 | |
| detailled? | 01/01/70 00:00 | |
| ? | 01/01/70 00:00 | |
| WOM | 01/01/70 00:00 | |
| Hoorah for Winbonds | 01/01/70 00:00 | |
| a timing error that | 01/01/70 00:00 | |
| CHPCON writes | 01/01/70 00:00 | |
| other use of CHPCON | 01/01/70 00:00 | |
| where is the happy-end? | 01/01/70 00:00 | |
| the happy end | 01/01/70 00:00 | |
| oh... | 01/01/70 00:00 | |
| there was no problem | 01/01/70 00:00 | |
| ah, but then... | 01/01/70 00:00 | |
| an obnoxious interference | 01/01/70 00:00 | |
| the goo' ol' EMI... | 01/01/70 00:00 | |
| NOT EMI | 01/01/70 00:00 | |
| Ah... | 01/01/70 00:00 | |
| correction | 01/01/70 00:00 | |
if the customer complains... | 01/01/70 00:00 |