FYI: It's working now. The PIC code that came with the motor controller was
not I²C re-start aware.
I re-implemented the ISR to accept both stop/start and re-start sequences
before reading the slave's output. That did the trick.
Best,
Torsten
--
For more options, visit
Status Update (a bit off topic for beagleboard, I suppose):
I took the MPLABX PIC code that the PiBorg folks provided for their motor
controller and ported it to the sdcc compiler, so I have a chance to
understand what's going on.
Result is here:
https://github.com/tkurbad/PicoBorgRev_PIC
If
Hi Graham,
Am Montag, 15. Mai 2017 18:39:10 UTC+2 schrieb Graham:
>
> When they say drop the clock speed on the bus, I am sure they mean to drop
> it down to 50kbps or 10 kbps, and see if it starts working.
> As a diagnostic, that would be strong indication of a timing problem in
> the PIC
Hi Graham,
just for reference: The guys who built the motor controller confirmed that
they are having trouble with newer kernels on the Raspberry PI, too.
https://www.piborg.org/node/2428
They say it's probably a timing issue. And with all the information I
collected so far I must assume they
Hi again,
this morning, I connected another IMU unit (Polulu AltIMU10 v5) in parallel
to the motor controller on I²C bus #1.
It works flawlessly and I can read the ID of the accel/gyro unit using
i2cget:
tkurbad@beaglebone:~/projects/mipSIE/python3$ i2cget -y 1 0x6b 0x0f
0x69
However, I still
Hi again,
Do you have another "trusted" I2C device you could parallel across the bus
> as a test device?
> I use an MCP9808 temperature sensor on most of my boards when bringing up
> a new design.
>
I think I'll do that on Monday, when I'm near my Beaglebone again,
Or as suggested by David,
Hi Graham,
Am Freitag, 12. Mai 2017 17:05:55 UTC+2 schrieb Graham:
>
> It looks like the MPU9250 has a non standard (to my way of thinking) I2C
> read sequence that requires you to resend the register address as part of a
> consolidated write/read sequence. The default tool i2cget does not
Update: I lowered the clock frequency of i2c1 to 100kHz via the dtb. That
also doesn't change the behaviour.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this
Hi Graham + William,
thank you for getting back to me so quickly.
The device I'm trying to communicate with is this motor controller:
https://www.piborg.org/picoborgrev/specs
It's made for the Raspberry PI, but I don't see any reason for it not to
work with the Beaglebone Blue.
With the help
Hi,
two weeks ago I received my BeagleBone Blue.
So far, I've managed to get
- an OrangeRX DSMX receiver
- a GP-735T GPS receiver
- a Servo
- and a 2S LiPo Akku
going, more or less without any problems.
However, all the I²C devices I connected to the available I²C bus #1 so far
only
10 matches
Mail list logo
