Workflow about bl_iot_sdk HOT 3 OPEN

Well, PineCone have USB-C connector. About the program and all other things, I'm waiting at the moment for EVB too, so I can't verify, but it should come in near days, so will reply here with my discovery.

from bl_iot_sdk.

Prefer "cross build from a host computer" to "an intel PC". This could be done (with enough determination) from an ARM chromebook or an Apple Silicon Mac, when such things aren't covered by NDA. It could certainly be done on an AMD station today.

Confirmed: there is no BLFlashEnv in the tree. Maybe that's part of #25.

Yay for USB-C. The pictures I'd seen were USB-Micro B and that was a drag.

from bl_iot_sdk.

The Linux Binary from #25 is something else. I noticed that when building from Debian 9:

bl_iot_sdk/customer_app/bl602_demo_event$ ./genromap 
****** Please SET BL60X_SDK_PATH ******
****** Trying SDK PATH [/opt/bl_iot_sdk/customer_app/bl602_demo_event/../..]
use exsting version.txt file
[5519] Error loading Python lib '/tmp/_MEIcjzmxP/libpython3.7m.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/_MEIcjzmxP/libpython3.7m.so.1.0)
/opt/bl_iot_sdk/customer_app/bl602_demo_event/../../make_scripts_riscv/project.mk:190: recipe for target 'all' failed
make: *** [all] Error 255

Apparently, it's needed for building and not flashing. It seems to be picky on the libc version. Because of that binary, I mentioned "intel PC", but I meant it in the broader sense.

Note, that's the command in ./genromap that bails out on old libcs:

$ cd bl_iot_sdk/image_conf; ./flash_build bl602_demo_event BL602
[15980] Error loading Python lib '/tmp/_MEIEMeqv3/libpython3.7m.so.1.0': dlopen: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /tmp/_MEIEMeqv3/libpython3.7m.so.1.0)

from bl_iot_sdk.