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 Timeout #13

Open
trish5000 opened this issue Apr 15, 2020 · 1 comment
Open

SPI Timeout #13

trish5000 opened this issue Apr 15, 2020 · 1 comment

Comments

@trish5000
Copy link

I'm having an issue where the SPI communication times out after 32 bytes.. Documentation for this boards is obviously slim.. any idea why that might be or is it a bug?
@momokang0614
Copy link

i have the same problem，did you solved？

mr-nice pushed a commit to mr-nice/spi-ch341-usb that referenced this issue Oct 19, 2023
@bibimbop
Rework i2c part to use one segment per transfer
35ae155 
Using requests with multiple 32-byte segments doesn't always
work. Split very transaction in segments of 32 bytes. For the writes,
check that devce chip is ready to process it first. For the read, ask
a status byte for every segemnt.

This fixes 24C eeprom writes, as well as i2cdetect.

  # i2cdetect -r 1
  WARNING! This program can confuse your I2C bus, cause data loss and worse!
  I will probe file /dev/i2c-1 using receive byte commands.
  I will probe address range 0x08-0x77.
  Continue? [Y/n]
       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
  00:                         -- -- -- -- -- -- -- --
  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  70: -- -- -- -- -- -- -- --

  # i2cdetect -q 1
  WARNING! This program can confuse your I2C bus, cause data loss and worse!
  I will probe file /dev/i2c-1 using quick write commands.
  I will probe address range 0x08-0x77.
  Continue? [Y/n]
       0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
  00:                         -- -- -- -- -- -- -- --
  10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
  70: -- -- -- -- -- -- -- --

Issue gschorcht#13, based on PR gschorcht#7.
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
@momokang0614 @trish5000