Greybus for Zephyr broken in latest sdk-next
Greybus for zephyr application from modules/greybus
is broken in the latest sdk-next due to some problem or conflict in sdk-next
branch with upstream dynamic thread support. The output I get is as follows:
*** Booting Zephyr OS build bcf-sdk-0.2.1-3640-gb28c431f5e27 ***
[00:00:00.004,943] <dbg> greybus_service: greybus_service_init: Greybus initializing..
[00:00:00.005,035] <dbg> greybus_manifest: identify_descriptor: cport_id = 0
[00:00:00.005,035] <dbg> greybus_manifest: identify_descriptor: cport_id = 1
[00:00:00.005,065] <dbg> greybus_manifest: identify_descriptor: cport_id = 2
[00:00:00.005,126] <dbg> greybus_transport_tcpip: gb_transport_backend_init: Greybus TCP/IP Transport initializing..
[00:00:00.005,340] <inf> greybus_transport_tcpip: CPort 0 mapped to TCP/IP port 4242
[00:00:00.009,735] <inf> greybus_transport_tcpip: CPort 1 mapped to TCP/IP port 4243
[00:00:00.009,979] <inf> greybus_transport_tcpip: CPort 2 mapped to TCP/IP port 4244
[00:00:00.009,979] <err> greybus_transport_tcpip: pthread_create: 22
[00:00:00.010,467] <err> greybus_service: failed to get transport
The zephyr version shown for this build is 3.4.0
and the last commit is b28c431f5e27f7579bb10118ef5e36bb4fa1322c
.
The last working zephyr version for greybus-for-zephyr (that I know of) is 3.4.0
with sdk-next commit e76584f824c8ca99f256b9e781cfdad316b9fd8f
.
It's possible that out of tree pthread patches that were being used are causing problem.