The libedgetpu can't be build by the "./balena-yocto-scripts/build/barys -d -m coral-dev" command

[yishinhung]

Hi
I build the balena-coral project by the "./balena-yocto-scripts/build/barys -d -m coral-dev" but i can't found any libedgetpu files or libraries in the build folder. Whether i miss some command about this? How can i build the libedgetpu or python3-edgetpu libraries to the balena-coral image?

Thank a lot!

[acostach]

Hi @yishinhung , libedgetpu files and libraries are not part of the Balena host operating system, instead they get installed in the application containers. See this example: https://github.com/balena-io-examples/coral-streaming-object-detector

[yishinhung]

Hi @yishinhung , libedgetpu files and libraries are not part of the Balena host operating system, instead they get installed in the application containers. See this example: https://github.com/balena-io-examples/coral-streaming-object-detector

Hi @acostach I try to run the example by "balena push" command on ubuntu PC. The logs always keep in "Device state settled"and don't execute the example functions. And, the uart console show the following logs. Could you give me some suggestion for this?
Thank lot!

root@balena:~# [ 240.266582] IPv6: ADDRCONF(NETDEV_UP): br-f3a511f083ae: link is not ready
[ 240.906294] br-f3a511f083ae: port 1(veth4e11403) entered blocking state
[ 240.913095] br-f3a511f083ae: port 1(veth4e11403) entered disabled state
[ 240.920600] device veth4e11403 entered promiscuous mode
[ 240.927405] IPv6: ADDRCONF(NETDEV_UP): veth4e11403: link is not ready
[ 240.933981] br-f3a511f083ae: port 1(veth4e11403) entered blocking state
[ 240.940698] br-f3a511f083ae: port 1(veth4e11403) entered forwarding state
[ 240.948147] br-f3a511f083ae: port 1(veth4e11403) entered disabled state
[ 242.440108] eth0: renamed from veth94b74f8
[ 242.472020] IPv6: ADDRCONF(NETDEV_CHANGE): veth4e11403: link becomes ready
[ 242.479222] br-f3a511f083ae: port 1(veth4e11403) entered blocking state
[ 242.486138] br-f3a511f083ae: port 1(veth4e11403) entered forwarding state
[ 242.494495] IPv6: ADDRCONF(NETDEV_CHANGE): br-f3a511f083ae: link becomes ready
[ 243.682299] br-f3a511f083ae: port 1(veth4e11403) entered disabled state
[ 243.689509] veth94b74f8: renamed from eth0
[ 243.749299] br-f3a511f083ae: port 1(veth4e11403) entered disabled state
[ 243.757708] device veth4e11403 left promiscuous mode
[ 243.762905] br-f3a511f083ae: port 1(veth4e11403) entered disabled state

[acostach]

Hi @yishinhung , when the build triggered by balena push is finished, the supervisor will download the built image and will run that container. This is visible in the dashboard, in the application you downloaded the image from. Based on the logs, it's possible that your container may be restarting because the CMD in your Dockerfile may be crashing. You can see if this is the case in the dashboard.