| ??? 08/24/09 13:01 Read: times |
#168512 - That's _too_ limited... Responding to: ???'s previous message |
Matthew Milford said:
That sends me back to the drawing board. I guess I could use regular RAM and just store a 00h or 01h, using a full byte for each note (seems wastefull) Any reason why not? Well, you said it - it's wasteful. As long as you don't need to store anything else in RAM, such an approach will work, however. You could also access singe bits by masking them, or write assembly functions to set/clear/read bit memory by an index (hint: the '51 can do indexed jumps). |
| Topic | Author | Date |
| Addressing bit memory indirectly | 01/01/70 00:00 | |
| Not possible. | 01/01/70 00:00 | |
| so why Bit addressable memory? | 01/01/70 00:00 | |
| sure you can and THINK | 01/01/70 00:00 | |
| Fast and saves code and RAM space | 01/01/70 00:00 | |
| No such instruction... | 01/01/70 00:00 | |
| Thanks so much | 01/01/70 00:00 | |
| That's _too_ limited... | 01/01/70 00:00 | |
| Not vast - actually quite small. | 01/01/70 00:00 | |
| bible time | 01/01/70 00:00 | |
| store bit address... | 01/01/70 00:00 | |
| Thanks | 01/01/70 00:00 | |
| if '2051' is the Atmel, then | 01/01/70 00:00 | |
| "cable" only for the "S" | 01/01/70 00:00 | |
| I second the motion and add | 01/01/70 00:00 | |
| I have... | 01/01/70 00:00 | |
| Smoking bad for the health | 01/01/70 00:00 | |
| an issue many newbies are not aware of is ... | 01/01/70 00:00 | |
| NXP??? | 01/01/70 00:00 | |
| Design flaw? | 01/01/70 00:00 | |
| a feature | 01/01/70 00:00 | |
| cheap | 01/01/70 00:00 | |
Code: Addressing bit memory indirectly | 01/01/70 00:00 |