by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jun 29 14:32
    nrobinson2000 closed #44
  • Jun 29 14:32
    nrobinson2000 closed #31
  • Jun 29 14:31
    nrobinson2000 closed #46
  • Jun 29 02:00
    shivams commented #46
  • Jun 28 18:01
    nrobinson2000 commented #46
  • Jun 28 17:18
    shivams opened #46
  • Jun 21 04:21

    nrobinson2000 on master

    Update README.md (compare)

  • Jun 21 04:11
    nrobinson2000 closed #32
  • Jun 21 04:10
    nrobinson2000 closed #40
  • Jun 21 04:10
    nrobinson2000 closed #37
  • Jun 21 04:09
    nrobinson2000 commented #44
  • Jun 21 04:08
    nrobinson2000 closed #7
  • Jun 21 04:07
    nrobinson2000 closed #17
  • Jun 21 04:07
    nrobinson2000 closed #18
  • Jun 21 04:07
    nrobinson2000 closed #24
  • Jun 21 04:06
    nrobinson2000 commented #31
  • Jan 20 2019 03:23
    nrobinson2000 commented #44
  • Jan 05 2019 04:37
    nrobinson2000 deleted #29
  • Jul 21 2018 18:34

    nrobinson2000 on get

    [skip ci] at 14:34 of 2018-07-21 (compare)

  • Jul 21 2018 18:33

    nrobinson2000 on get

    [skip ci] at 14:33 of 2018-07-21 (compare)

Thorsten von Eicken
@tve
Kevin McQuown
@iitgrad
how do I get po-util to know about the mesh Gen 3 products. I'm getting ./build/platform-id.mk:72: *** "Unknown platform: xenon. Stop. when doing a build
Thorsten von Eicken
@tve
po boron flash-beta
Nathan Robinson
@nrobinson2000
Have you done the following?
po config v0.8.0-rc.27
po setup-mesh
Thorsten von Eicken
@tve
quick Q: are those two commands global or per application directory?
Nathan Robinson
@nrobinson2000
Global
I'd like to make a per application option in the future
Jeremy Ellis
@hpssjellis
Does po have knowledge of the latest releases? is the newest one called po config v1.1.0-rc.1
Nathan Robinson
@nrobinson2000
Yes. You may need to do po update first so it can grab the latest releases.
Jeremy Ellis
@hpssjellis

Hi Nathan: I am installing po on a cloud Docker environment using this Dockerfile command:

RUN apt-get update                                                                                               \
    && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends dbus gcc g++ automake           \
               libtool lsb-release make  clang-format-6.0   libdbus-1-dev libboost-dev libreadline-dev           \                                     
               autoconf autoconf-archive  software-properties-common bsdtar                                      \
               sudo curl git gzip python gnupg2 software-properties-common build-essential libarchive-zip-perl   \
    && apt-get update                                                   \
    && /bin/bash -c "bash <(curl -sL https://particle.io/install-cli)"  \
    && /bin/bash -c "bash <(curl -sL get.po-util.com)"                  \
    && po                                             \
    && chown -R gitpod:gitpod /home/gitpod/.po-util   \
    && chmod -R 777 /home/gitpod/.po-util

and building using these commands

po init argon myProjectName
cd myProjectName

po config mesh-develop

po setup-mesh

MODULAR=n po argon build

but I get this error, which is not a fault of Po I simply haven't installed a needed dependency, just not sure what it would be.


mbedtls/library/oid.c:558:31: error: 'oid_cipher_alg' defined but not used [-Werror=unused-const-variable=]
 static const oid_cipher_alg_t oid_cipher_alg[] =
                               ^~~~~~~~~~~~~~
mbedtls/library/oid.c:295:39: error: 'oid_ext_key_usage' defined but not used [-Werror=unused-const-variable=]
 static const mbedtls_oid_descriptor_t oid_ext_key_usage[] =
                                       ^~~~~~~~~~~~~~~~~
mbedtls/library/oid.c:167:30: error: 'oid_x520_attr_type' defined but not used [-Werror=unused-const-variable=]
 static const oid_x520_attr_t oid_x520_attr_type[] =
                              ^~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make[2]: *** [../../build/module.mk:272: ../../build/target/mbedtls/platform-12/./mbedtls/library/oid.o] Error 1
make[1]: *** [../build/recurse.mk:12: third_party/mbedtls] Error 2
make: *** [../build/recurse.mk:12: crypto] Error 2
Nathan Robinson
@nrobinson2000

Does installing these packages help?:

sudo apt-get install gcc-multilib libncurses5:i386

https://docs.particle.io/support/particle-tools-faq/workbench/#linux-tips

In the future, I'd like to reduce the overhead of po-util a lot by having it rely more on components from particle-cli and Workbench.
Jeremy Ellis
@hpssjellis
Thanks for the suggestions. I will try them out. My Dockerfile actually installs for Openthread and po so it has a fair bit of overhead. Actually takes a fair bit of time to load.
Jeremy Ellis
@hpssjellis
My docker build can't find libncurses5:i386 I will look into a solution. For openthread I also could not install libreadline and libglib2.0-dev if that is relevant
Jeremy Ellis
@hpssjellis
Looks like particle doesn't totally hate me. They want to see my openthread methods https://community.particle.io/t/using-particle-mesh-devices-with-the-openthread-border-router/46189/68
Nathan Robinson
@nrobinson2000
I saw your post earlier today. I'm pretty sure Brandon is going to try replicating your setup in Workbench.
Jeremy Ellis
@hpssjellis
image.png
My cloud attempt at po-util is coming along. I am still making some changes. any idea what might be causing this issue.
mbedtls/library/oid.c:295:39: error: 'oid_ext_key_usage' defined but not used [-Werror=unused-const-variable=]
static const mbedtls_oid_descriptor_t oid_ext_key_usage[] =
^~~~~
mbedtls/library/oid.c:167:30: error: 'oid_x520_attr_type' defined but not used [-Werror=unused-const-variable=]
static const oid_x520_attr_t oid_x520_attr_type[] =
^~~~~~
cc1: all warnings being treated as errors
make[2]: [../../build/module.mk:272: ../../build/target/mbedtls/platform-12/./mbedtls/library/oid.o] Error 1
make[1]:
[../build/recurse.mk:12: third_party/mbedtls] Error 2
make: * [../build/recurse.mk:12: crypto] Error 2
They are only warning, any idea how to suppress warnings as errors?
Jeremy Ellis
@hpssjellis
Not really sure which make file needs this but it might suprress the warning
-Wno-unused-const-variable
Jeremy Ellis
@hpssjellis
I think I know what is happening, not sure where po-util stores the gcc make files that are used. any suggestions?
Jeremy Ellis
@hpssjellis
I think I asked this before but can't find your reply, where are the src and make files stored that po compiles? Strangely hard to find. Can't even find the particle version of openthread.
Nathan Robinson
@nrobinson2000
Are you referring to ~/.po-util/src/particle/firmware ?
@hpssjellis
I saw your video today, very nice.
Jeremy Ellis
@hpssjellis
Thanks. Better news. I got cloud po-util working! Open in Gitpod
Jeremy Ellis
@hpssjellis
Best thing is it works on my Particle build. I am probably going to change the github a fair bit but it is here https://github.com/hpssjellis/gitpod-po-util
emdash
@emdash
I am pulling my hair out with Particle and external libraries. I would really like is some minimal Makefile that builds exactly the sources I specify against the Particle toolchain, but without all the dependency management. I would prefer to manage dependencies via git submodules, and not be endlessly copying files around or having libraries silently "upgraded" behind my back.
Is this even possible?
I am not having much luck with workbench, and from what I can tell, po-util works in a similar way. But I figure @nrobinson2000 probably knows more about the particle toolchain than anyone else at this point
Jeremy Ellis
@hpssjellis
Not sure if this is helpful but I just found out about platformio.org and with the particle debugger board $20 it seems to work with the xenon, possibly the Argon.
emdash
@emdash
@hpssjellis I'll take a look
Nathan Robinson
@nrobinson2000

@emdash Long before Particle created the updated library structure that is used by Workbench and particle-cli, I had developed my own system for managing a centralized directory of installed libraries that would get symbolically linked into each project directory. When Particle announced the new structure for libraries I decided to add compatibility for the structure to po-util by integrating workbench's makefile. My old (legacy) system still exists within po-util.

I agree that it would be better for Workbench/particle-cli to utilize a local centralized directory of libraries instead of requiring users to make a copy of a library in each project.

I have been dreaming of creating new utility similar to po-util that would make use of more of the new tools that Particle is developing, but I'm not sure if it would be necessary if Particle added the features to the tools themselves.

@emdash Could you describe your situation a little bit more? I just made a repository to test using a library as a git submodule and it works pretty well. https://github.com/nrobinson2000/submodule-test

Blake Bourque
@TechplexEngineer
I just installed the SparkIntervalTimer library "po lib add SparkIntervalTimer", I see the new directory with the library but when I build I get a mesage "SparkIntervalTimer.h no such file or directory" However that file is clearly in the SparkIntervalTimer folder. What am I missing?
Selection_262.png
Nathan Robinson
@nrobinson2000

I'm getting the same issue. It's probably something to do with the symbolic links. Personally I've switched to using the official Particle structure for all of my projects because of its interoperability with Workbench and particle-cli. I would like to make a system that uses git submodules in the future.

If I use SparkIntervalTimer in an officially structured project it works fine:

particle project create --name interval-test .
cd interval-test
particle library copy SparkIntervalTimer
mv src/interval-test.ino src/interval-test.cpp
vim src/interval-test.cpp # Load in demo
po photon build-beta
Nathan Robinson
@nrobinson2000

To anyone who still uses this gitter, I am proud to release neopo, a replacement for po:

https://community.particle.io/t/neopo-a-lightweight-solution-for-local-particle-development/56378