The documentation for symbiosis was updated: Symbiosis: Source code and documentation - #28 by tomin
I only took a quick glance, but from what I saw, you can add the target addresses of all your devices on the TOH bus through config files. I wonder: Could these configs also be created and loaded/unloaded dynamically (i.e. non-persistent)? I’m again referring to a set of command line tools that let you easily talk to several I2C/I3C devices on the TOH bus, even when the identification EEPROM is not present. For example when you are in prototyping phase and just plugged some components together on a breadboard in a quick-and-dirty manner. And then, without having to write any config files first, simply start a terminal and manually hack in some commands (or execute a shell script) for testing your circuit on-the-fly. The following is a very simple mockup.
Switch on the power supply to the TOH:
toh-interface --power on
Borrow access to the I2C/I3C targets you want to interact with (NB: I’m assuming here that using different clock speeds for every target on the bus doesn’t cause hickups hardware-wise, but I might be wrong):
toh-borrow --target 0x1A --type I2C --speed 400kHz
toh-borrow --target 0x3C --type I2C --speed 1MHz
Now we can interact with these 2 devices from our terminal by using the toh-read and toh-write commands from my previous post (without the --speed parameter) in whatever way we want.
When finished, properly return the borrowed devices…
toh-return --target 0x1A --target 0x3C
…and switch off the power supply to the TOH:
toh-interface --power off
Such a workflow would be a tremendous help, especially during TOH development. And it adheres to the KISS principle when you just don’t want to deal with D-Bus and friends yourself (like me
). Instead, the mentioned command line tools will do the heavy lifting for you in this regard. Even for productive operation after development is finished - for simple TOH designs at least.
@poetaster: Are you maybe interested to carry this idea to one of the community meetings (if you think that it’s also useful for you)? Electronics and MCU development is not my profession, so I surely couldn’t have that kind of sophisticated tech-talk with the people at Jolla compared to you.