Timeline for Unexpected bits when shifting out (ATtiny85)
Current License: CC BY-SA 3.0
14 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 19, 2017 at 11:21 | history | tweeted | twitter.com/StackElectronix/status/887633409433980928 | ||
Jul 19, 2017 at 1:29 | vote | accept | Protecto | ||
Jul 19, 2017 at 1:29 | comment | added | Protecto | Yeah, I was too sure about that part of my code and didn't even check it. Thanks @brhans for pointing it out. | |
Jul 19, 2017 at 1:18 | answer | added | brhans | timeline score: 4 | |
Jul 19, 2017 at 1:10 | comment | added | vicatcu | Good eye @brhans | |
Jul 19, 2017 at 1:03 | comment | added | brhans | Your 'Correct' sequence is not actually correct - according to the code you've written. You're starting with the Least Significant bit from each data byte, so what you should see with that code is 0, 1, 0, 1, 0, 1, 0, 1, etc - not 1, 0, ... | |
Jul 19, 2017 at 1:03 | answer | added | vicatcu | timeline score: -1 | |
Jul 19, 2017 at 1:01 | comment | added | vicatcu | What happens if you out data in RAM instead of flash? | |
Jul 19, 2017 at 0:30 | history | edited | Protecto | CC BY-SA 3.0 |
edited title
|
Jul 18, 2017 at 23:44 | history | edited | Protecto | CC BY-SA 3.0 |
add real data
|
Jul 18, 2017 at 23:42 | comment | added | Protecto | Thanks for your reply! Sleeping doesn't impact this behavior, I've checked. The actual wrong sequence is repeated the same even after 2nd, 3rd, 4th, etc. cycle. | |
Jul 18, 2017 at 23:22 | comment | added | Asmyldof | To start, unless you turn that off with directives, your attempt of "if(==255) =0; else ++" will be optimised to just ++ by the compiler, because it's a cleverclogs, so that will indeed make no difference at all. Do these fixed positions happen consistently even if bit has wrapped around. I.e. at 5th byte and 37th byte, etc, or does the location in your 32byte series change after a wrap? Try what happens if you don't sleep the controller. It's been long since I used the x5 series, so can't remember, but there may be issues with some sleep states and missed IRQs in a few "older" Tinies. | |
Jul 18, 2017 at 23:02 | history | edited | Protecto | CC BY-SA 3.0 |
added 29 characters in body
|
Jul 18, 2017 at 22:54 | history | asked | Protecto | CC BY-SA 3.0 |