Temporarily adding this issue to track mikroBUS over Greybus steps to reproduce, not able to reproduce the buildroot setup still and is failing as before, can you point me on how I should update the beagleconnect repo for steps to repoduce the results?
For now an out of tree Greybus+mikroBUS modules are available/patches are added to bb-kernel repo, the changes are being added here:
The overlay for SensorTag sample(both UART, NET[2.4G] tested) adds the devices on board(OPT3001) and few added Click Boards, all the devices were tested in Polling/no IRQ mode.
Once the changes are taken the steps to reproduce are very similar to the normal Greybus Sample(mikrobus needs to be probed at host additionally)
For build and flash TCP/IP NET 2.4GHz Sample:
Hi @jadonk,
Temporarily adding this issue to track mikroBUS over Greybus steps to reproduce, not able to reproduce the buildroot setup still and is failing as before, can you point me on how I should update the beagleconnect repo for steps to repoduce the results?
For now an out of tree Greybus+mikroBUS modules are available/patches are added to bb-kernel repo, the changes are being added here:
Devices are described over Zephyr DT, the device tree binding for the same is available here: https://github.com/vaishnav98/greybus-for-zephyr/blob/mikrobus/dts/bindings/greybus/zephyr%2Cgreybus-device.yaml
The overlay for SensorTag sample(both UART, NET[2.4G] tested) adds the devices on board(OPT3001) and few added Click Boards, all the devices were tested in Polling/no IRQ mode.
Once the changes are taken the steps to reproduce are very similar to the normal Greybus Sample(mikrobus needs to be probed at host additionally) For build and flash TCP/IP NET 2.4GHz Sample:
For build and flash UART Sample:
At host:
Here is a quick demo with PocketBeagle + ATUSB and CC1352R SensorTag : https://youtu.be/JKrCRRuCw3c?t=143
TODO: