Timeline for PIGPIO wiring, basic i2c slave questions
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 7, 2018 at 11:10 | comment | added | Ebya | sorry to spam you, I'm stuck on updating the txBuf for a week now, see my other question. | |
| Apr 29, 2018 at 13:40 | comment | added | joan | @Ebya It doesn't exist. bsc_i2c is a trivial wrapper around bsc_xfer. | |
| Apr 29, 2018 at 12:38 | comment | added | Ebya | I saw that my only problem reside in ”bsc_i2c" not existing in C, or is it just the API ref missing it? | |
| Apr 29, 2018 at 11:48 | comment | added | joan | @Ebya See raspberrypi.stackexchange.com/a/57093/13650 | |
| Apr 29, 2018 at 11:07 | comment | added | Ebya | I'm stuck on how to properly send data as a slave, if you have an example on any languages, I'ld like a link | |
| Apr 26, 2018 at 8:20 | vote | accept | Ebya | ||
| Apr 26, 2018 at 8:20 | comment | added | Ebya | disreagard comment, the doc doesn't refer to the gpio pin number but to the actual name of the pin... got it working | |
| Apr 26, 2018 at 8:11 | comment | added | Ebya | Just tested not receiving anything, joining a picture to the OP in a minute or two. | |
| Apr 26, 2018 at 8:10 | comment | added | joan | @Ebya That I understand. It's easy to miss within the other text. For examples it's often worth looking at the documentation for the other languages, in particular pigs or Python. They are often more detailed than the C examples. | |
| Apr 26, 2018 at 8:05 | comment | added | Ebya | I must admit that I read that page and didn't find it, I blame my lack of sleep, testing that now | |
| Apr 26, 2018 at 7:59 | history | answered | joan | CC BY-SA 3.0 |