Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 20 03:23
    nrobinson2000 commented #44
  • Jan 05 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)

  • Jun 28 2018 22:48

    nrobinson2000 on gh-pages

    at 18:48 of 2018-28-06 (compare)

  • Jun 28 2018 22:46

    nrobinson2000 on master

    Update README.md (compare)

  • Jun 28 2018 22:34

    nrobinson2000 on master

    Update README.md (compare)

  • Jun 24 2018 22:46
    nrobinson2000 commented #37
  • Jun 21 2018 01:26
    nrobinson2000 commented #37
  • Jun 19 2018 13:25
    elec3647 commented #37
  • May 27 2018 22:23
    nrobinson2000 commented #45
  • May 26 2018 03:40

    nrobinson2000 on gh-pages

    at 23:40 of 2018-05-25 (compare)

  • May 26 2018 03:37

    nrobinson2000 on gh-pages

    at 23:37 of 2018-05-25 (compare)

  • May 16 2018 13:02

    nrobinson2000 on master

    at 09:02 of 2018-05-16 (compare)

  • May 16 2018 13:01

    nrobinson2000 on master

    at 09:01 of 2018-05-16 (compare)

  • May 12 2018 02:25
    robbielove closed #45
  • May 12 2018 02:25
    robbielove commented #45
  • Apr 24 2018 04:40
    nrobinson2000 commented #45
  • Apr 24 2018 03:06
    nrobinson2000 closed #43
  • Apr 24 2018 03:06
    nrobinson2000 commented #43
Thorsten von Eicken
@tve
(I'm not sure everything I typed into gitterm.im came across, the following line shows up in red for me, so I wonder whether it hit an error:
Yup, now I'm successful with po dfu open -d /dev/ttyACM0; po xenon flash-beta
)
Nathan Robinson
@nrobinson2000
dfu-util -l
This would only list the xenon when it's in dfu mode, which is expected.
po xenon flash-beta should automatically put the xenon into dfu for you as long as the xenon is the only /dev/ttyACM
Thorsten von Eicken
@tve
OK, but if I look in po-common, for dfu_open() the only condition that does anything without a -d is if the device is listed by dfu-util -l. I don't see how it can do anything useful unless the -d options is specified...
Where in the code does it look for /dev/ACM* ?
What do you think about the prebuild and postbuild prerequisites missing on program-dfu?
Nathan Robinson
@nrobinson2000
In po-linux line 432 it tries to find /dev/ACM*
Thorsten von Eicken
@tve
I see, I have a /dev/ttyACM1 that is something else and that messes it up.
Nathan Robinson
@nrobinson2000
Yeah
Thorsten von Eicken
@tve
Have you considered:
tve@soumak /h/s/g/p/gps-test> ls /dev/serial/by-id
usb-FTDI_FT232R_USB_UART_A1014JRC-if00-port0@
usb-Linux_4.4.13-ntc-mlc_with_musb-hdrc_CDC_Composite_Gadget-if02@
usb-Particle_Xenon_CDC_Mode_e00fce68a8f4dc1358b533f5-if00@
[tve@soumak ~]$ for modem in /dev/serial/by-id/usb-Particle*; do echo $modem; done
/dev/serial/by-id/usb-Particle_Xenon_CDC_Mode_e00fce68a8f4dc1358b533f5-if00
so you could do:
for modem in /dev/ttyACM* /dev/serial/by-id/usb-Particle*; do
I made that change locally and happiness ensues :-)
Uhh, not so fast, bash uglyness if that doesn't exist...
Nathan Robinson
@nrobinson2000
I did not know about /dev/serial/by-id/
Thorsten von Eicken
@tve

To catch ttyACM and by-id you need something along the lines of

[tve@soumak ~]$ for modem in /dev/ttyACM* /dev/serial/by-id/usb-Particle* foobar*; do [ -e $modem ]
&& echo modem is $modem; done
modem is /dev/ttyACM0
modem is /dev/ttyACM1
modem is /dev/serial/by-id/usb-Particle_Xenon_CDC_Mode_e00fce68a8f4dc1358b533f5-if00
[tve@soumak ~]$

(I added the foobar* to show that it works if there are no files matching the wildcard)

I now have:
for modem in /dev/ttyACM* /dev/serial/by-id/usb-Particle*; do
    if [ -e "$modem" ]; then
        MODEM="$modem"
        MODEM_DUO="$modem"
    fi
done
echo MODEM is set to $MODEM
dinner time here, thanks for your help!
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