Timeline for How to access GPIO pins on Atmega with memory mapping?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2019 at 1:00 | comment | added | C. K. | @ElliotAlderson I have investigated this and it's not possible to refer to each bit in a port with an address, only the address of the actual port. So that leaves me with using PORTB/C/D as just the same as using memory mapping techniques. | |
| Dec 13, 2019 at 20:16 | comment | added | C. K. | @Aaron I think this is close to what I wanna do. Will investigate it further. | |
| Dec 13, 2019 at 19:27 | comment | added | Elliot Alderson | Your suggestion doesn't seem to be the same as the original question. The OP was manipulating individual bits at a single address for each port but you seem to have a distinct address for each bit. I'm not very familiar with the AVR...can you explain how this would work? | |
| Dec 13, 2019 at 17:42 | comment | added | Aaron | If the OP had theLED hardware already in chip order, the question wouldn't exist. Also and optimized solution wasn't requested. | |
| Dec 13, 2019 at 17:36 | comment | added | Chris Stratton | That's rather wasteful, they already have a dense and contiguous order in the hardware. | |
| Dec 13, 2019 at 17:32 | history | answered | Aaron | CC BY-SA 4.0 |