Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

SPI writebytes / xfer / xfer2 clocks out arrays of bytes in reverse order #52

Closed
sidechained opened this issue Dec 29, 2013 · 1 comment
Closed

SPI writebytes / xfer / xfer2 clocks out arrays of bytes in reverse order #52

sidechained opened this issue Dec 29, 2013 · 1 comment

Comments

@sidechained
Copy link

Just wanted to open this as a separate issue, as I'm experiencing the same behaviour as tweekzilla as mentioned here:

#47

That is, that executing spi.writebytes([0x44, 0x88, 0xBB, 0xDD]) clocks out in reverse order (i.e. 0xDD, 0xBB, 0x44, 0x88). I can confirm the same behaviour with xfer and xfer2. Is this a problem with the spidev C++ implementation, or with the bindings?
@pdp7
Copy link
Collaborator

pdp7 commented Aug 20, 2016

@sidechained Could you please try again with the latest version and report if this is still an issue?

@pdp7 pdp7 closed this as completed Oct 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pdp7 @sidechained