MikroBus on BeaglePlay (old)

Does MikroBus socket allow for extension cable on BeaglePlay so two or more boards can be used. (Original question was wrong inasmuch there is no MikroBus connector on side) I have asked MikroBus people and yet to receive reply.

Received ProFET 15, Temp&Humi Click, Shuttle Click and two Shutles that purportedly will work together.

If I were to not go in for their dev environment and wanted to use modules or libs and gcc, what would I need to get from them?

It depends.

“Mikrobus” is just a combination of SPI + I2C + UART + GPIO + Analog pins. So SPI + I2C can be daisy chained, so if your MB board is using one of those then yes, you could “stack” multiple boards.

Likewise if your first MB board uses UART, you can stack a 2nd that uses SPI / I2C / etc…

About the only things you can’t stack is 2 or more boards trying to use UART or GPIO.

So are their libs and sdk useless for BeaglePlay and I better get busy if I want anything to work? All they have said is those boards are compatible to use together.

You can use a shuttle click to add multiple, but you need for the pins to not interfere. If each is I2C, there’s no problem. Only 1 can use UART or analog. If SPI, I think the shuttle cable might do something with the chip selects, but probably wouldn’t work.

The software support is mostly going to come from Linux drivers: Using mikroBUS — BeagleBoard Documentation.

Thanks, I must have gone to a wrong doc link for BeaglePlay as Mikro was todo

Where to read values from:

Library version: 0.24 (git tag: v0.24)
Compiled with backends: local xml ip usb
IIO context created with local backend.
Backend version: 0.24 (git tag: v0.24)
Backend description string: Linux BPLAY4DCA 5.10.168-ti-arm64-r108 #1bullseye SMP Fri Jul 28 17:37:55 UTC 2023 aarch64
IIO context has 2 attributes:
local,kernel: 5.10.168-ti-arm64-r108
uri: local:
IIO context has 1 devices:
iio:device0: adc102s051
2 channels found:
voltage1: (input)
2 channel-specific attributes found:
attr 0: raw value: 4068
attr 1: scale value: 0.805664062
voltage0: (input)
2 channel-specific attributes found:
attr 0: raw value: 0
attr 1: scale value: 0.805664062
No trigger on this device

Does no trigger mean I can’t read next value? I keep getting NULL for iio_device_create_buffer(dev, 1, false);

From Mikrobus on getting Temp and Humidity 15 to be read on BeaglePlay:

“We can not help you a lot here, as i said in one of our previous conversations, our compiler do not support Beagle at the moment”

I think they missed that I want to use gcc, too.

I was checking part numbers and realized this a TI ADC and not Mikrobus SHT40 at all.

[ 3.880782] mikrobus:mikrobus_port_register: registering port mikrobus-0
[ 3.880849] mikrobus mikrobus-0: mikrobus port 0 eeprom empty probing default eeprom

but I would think if working correctly it would show up in iio_info.

Continue on this thread: MikroBus on BeaglePlay 2 - #13 by jkridner