Hello,
I get the following compilation error for device-os:
make PLATFORM=photon
mkdir -p …/build/target/communication/platform-6-prod-6/src/#include “mbedtls/rsa.h”
And I can’t find rsa.h in the clone I’ve made of the git device-os repository. should the USE_MBEDTLS CFLAG really be defined during compile? Or am I missing something?
Thank you
HI @armystic
As a first step, can you please confirm you’ve updated your submodules with git submodule update --init --recursive before attempting make?
2 Likes
Thanks @mstanley , that indeed solved it.
I am now running into the following complaining MODULE_FUNCTION being undefined. I thought maybe specifying monolithic (MODULAR=n) would solve it as follows, but the problem still lingers:
make PLATFORM=photon MODULAR=n all#if MODULE_FUNCTION != MOD_FUNC_BOOTLOADER
Hey @armystic ,
Would you be interested in trying neopo?
It provides an incredibly straightforward interface for building Particle projects on the command line and manages local toolchains identically to Workbench.
As an experiment, I tried to replicate your build process and I get the same error about MODULE_FUNCTION.
#!/bin/bash
PATH="$PATH:/home/nrobinson/.particle/toolchains/gcc-arm/9.2.1/bin"
cd /home/nrobinson/.particle/toolchains/deviceOS/2.0.0-rc.3
make PLATFORM=photon MODULAR=n all
However, if I run make in the modules directory as suggested by the compile-all target in the Workbench makefile, make PLATFORM=photon MODULAR=n all runs successfully.
#!/bin/bash
PATH="$PATH:/home/nrobinson/.particle/toolchains/gcc-arm/9.2.1/bin"
cd /home/nrobinson/.particle/toolchains/deviceOS/2.0.0-rc.3/modules
make PLATFORM=photon MODULAR=n all
Edit: Sorry for not remembering that you had difficulties building roughly a month ago:
Hey @nrobinson2000
Thanks for your fine reply.
I had compiled some years ago on version 4.x of the toolchain and never encountered this issue. Note that my current version of the tool chain in higher than 9.2.1, so a bit strange.
Here is the output after a compile attempt, didn’t go very far:
~/Software/particle/device-os$ make PLATFORM=photon
Building firmware for Production Photon, platform ID: 6, product ID: 6
make -C ./communication
make[1]: Entering directory ‘~/Software/particle/d…
In all seriousness though, using neopo would allow you to easily setup the local Particle toolchain and get right to building firmware within a few minutes.
1 Like
Thank you @nrobinson2000 , changing to modules directory compiled without a hitch.
neopo is on my list of things to do. At this stage I'm using first principles, but will get to that. Looks like a very cool tool for particle development. Just wondering wouldn't Particle CLI (or Particle VS Studio) do the same thing and more? [I haven't installed or played with Particle VS yet]
And for the gcc toolchain, looks like it is very pedantic about the exact version, so had to install the 9.2.1 version to get any further
May I know where I find this Workbench makefile you refer to? I couldn't find any compile-all targets in makefiles under device-os
1 Like
When installing Workbench or neopo, the ~/.particle/toolchains directory is created and populated with all the required dependencies for local development, eliminating the need to hunt down specific versions of dfu-util, gcc-arm, or openocd:
~/.particle/toolchains/
├── buildscripts
│ └── 1.9.2
├── buildtools
│ └── 1.1.1
├── deviceOS
│ └── 3.0.0-beta.1
├── gcc-arm
│ └── 9.2.1
└── openocd
└── 0.11.2-adhoc6ea4372.0
The "Workbench makefile" is located at ~/.particle/toolchains/buildscripts/1.9.2/Makefile, and it is used internally by both Workbench and neopo to build Particle projects. Here is an online copy.
In a sense, yes. Neopo is an unofficial tool that is the culmination of several years of my efforts to simplify local Particle development at the command line.
Particle CLI does not yet deal with local development. You must upload your source code to Particle's servers and download the produced binary. You have less control over how your binary is produced.
Particle Workbench is an exceptional tool, but it requires Visual Studio Code to operate. In environments where running a large Electron application is unfeasible or undesirable, neopo is an excellent alternative, providing access to the same toolchains and makefile used by Workbench.
In addition to supporting most of the build features of Workbench, neopo provides a Python API for running neopo commands and using Particle CLI from within Python, creating limitless ways to automate Particle development.
Finally, tab completion is included with neopo, making it much easier to find suitable arguments. (If you're interested in tab completion for Particle CLI, I've made a script for that as well. )
1 Like
Thank you @nrobinson2000 . A light-weight local development tool is great, so neopo sounds like just the right tool. So as you explain this tool uses ~/.particle; this would not interfere with a parallel version of local development (in another space) directly from command line would it? Are you saying that ~/.particle gets created by either neopo or the Workbench?
1 Like
system
August 14, 2021, 3:11am
9
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.
