This causes by ea7cea6c8a7e7184f275a9a56cfa6873b1716e1c and following df59d82772fd67b8fc1d30d97917305be0f49675
@brgl@agherzan I think we should change the behaviour of the switch. CI should add ONIRO_ENABLE_ACM0 or similar not users add ONIRO_NO_ACM0 to make blinky working again
@lucafavaretto workaround is as simple as: echo ONIRO_NO_ACM0 = "1" >> conf/local.conf
@lucafavaretto This is not a regression though - it used to work like that ever since I started working on oniro zephyr. The app waits for the ACM0 to be opened on the host. The QA team asked me explicitly to keep it this way.
@brgl can you elaborate please? which QA team? Both Oniro and Zephyr have in their documentation something like "After flashing, the LED starts to blink. Blinky does not print to the console.". from user's point of view this "feature" is completely broken.
As I mentioned this logic should be reverted to "blink by default", wait for connection if flag has been specified
@landgraf if you take current dunfell oniro and build the blinky image, it won't start blinking until you start a console on the ACM0 device. It was Chase Qi who requested it be kept the same in kirkstone IIRC. I don't often look at the docs but maybe they're wrong. I agree it's a broken idea hence this variable.