PPK2 via python in Linux of Chromebook

[AlexanderOhm]

Hi!
I want to run the PPK2 via the python API from a virtual env in the linux container of a Chromebook. Is this possible?

When I plug in the kit and select "connect to linux" i can list it in lsusb. However, if I try list_devices() from the API i get nothing, just []. I tried creating a udev rule that sets access to the PPK2, but I can't see anything happening in udevadm monitor when i plug in the device, something with the Chromebook environment? I did install nrf connect desktop for linux, and the PPK app(?). From the gui software i can select the device, but i cant fully connect to it. It gets stuck at opening device with S/N ...

Any ideas? Thoughts?

(venv-compact) aquaroburproductiontest1@penguin:~/compact-rig/python-hw-test$ python3
Python 3.11.2 (main, Mar 13 2023, 12:18:29) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> PPK2_API.list_devices()
KeyboardInterrupt
>>> import ppk2_api
>>> from ppk2_api.ppk2_api import PPK2_API
>>> PPK2_API.list_devices()
[]
>>>
[2]+  Stopped                 python3
(venv-compact) aquaroburproductiontest1@penguin:~/compact-rig/python-hw-test$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 1915:c00a Nordic Semiconductor ASA PPK2
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
(venv-compact) aquaroburproductiontest1@penguin:~/compact-rig/python-hw-test$ cat /etc/udev/rules.d/98-nrf-ppk2.rules
SUBSYSTEM=="usb", ATTRS{idVendor}=="1915", ATTRS{idProduct}=="c00a", MODE="0666"

[runsiv]

Hi Alexander,

Which os are you running on the chromebook? 

Have you installed nRF Command Line Tools and the udevtool? 

Regards

Runar

[AlexanderOhm]

Hi!,
I am running ChromeOS 121.0 (latest).

I installed the CLI tools but was unaware of the udevtool. I will try that now and report back momentarily.

[runsiv]

I can't unfortunately not make any promises regarding if it will work or not. The only Linux system we test our sw on Ubuntu as you can see here

Regards

Runar

[AlexanderOhm]

I installed the udevtool and rebooted. No change.

As a side note i did set access to the kit under Settings>Linux>Manage USB devices too.

[runsiv]

I'm afraid I can't really be more helpful as we don't support ChromeOS. I checked if I could find any other case with some information but I could not

Regards

Runar

[AlexanderOhm]

Thanks. I will ditch the chromebook.

For reference, we were hesitant at first when chromebook was pitched, but verified a lot of other functionality regarding flashing/provisioning and otherwise handling nrf chips and our pcbs. But this is perhaps finally a roadblock. Thank you for your effort.

[runsiv]

Happy to help, best of luck going forwards. i will just close this ticket

Regards

Runar