??? 03/01/07 23:04 Read: times |
#134064 - the vdd monitor? Responding to: ???'s previous message |
Why does the vdd monitor need to be utilized for flash erase/writes? Just as an FYI, my SiLabs is battery powered so I really doubt that there's anything unstable with Vdd, though I can check with a scope when I get home. Any other suggestions for why my code doesn't work/why the processor gets hung after the mov @dptr, whatever instruction? Thanks,
D |
Topic | Author | Date |
Writing to flash from firmware | 01/01/70 00:00 | |
pretty sure the problem is in the erase section... | 01/01/70 00:00 | |
that's another thing ... | 01/01/70 00:00 | |
this is the case when the comment IS harmful.. :-) | 01/01/70 00:00 | |
need some sleep? | 01/01/70 00:00 | |
haha, yes | 01/01/70 00:00 | |
Key sequence | 01/01/70 00:00 | |
Thanks rob | 01/01/70 00:00 | |
"hung up"? | 01/01/70 00:00 | |
14 bytes or 15? | 01/01/70 00:00 | |
Another case where the comment is harmful :-( | 01/01/70 00:00 | |
More suggestions | 01/01/70 00:00 | |
random thought | 01/01/70 00:00 | |
RE: random thought | 01/01/70 00:00 | |
What I mean by hung up | 01/01/70 00:00 | |
since I do not use this deviate | 01/01/70 00:00 | |
the vdd monitor? | 01/01/70 00:00 | |
how you determine? | 01/01/70 00:00 | |
In response to Oleg's question | 01/01/70 00:00 | |
seen this app note? | 01/01/70 00:00 | |
problem solved... | 01/01/70 00:00 | |
are you using LARGE? | 01/01/70 00:00 | |
no large or xdata var![]() | 01/01/70 00:00 |