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)

Jeremy Ellis
@hpssjellis
Ugh. I did fresh installs of ubuntu 16.04 but it never updated. Just found out I have 267 out of date files. That is probably my issue. By the way have you tried Bash on Windows? I got po-util installed even particle-cli worked but it could not compile the particle code. Would be great if po-util worked on a windows machine.
Nathan Robinson
@nrobinson2000
There's demand for it but I haven't had the time to officially support Windows yet.
Jeremy Ellis
@hpssjellis
Since po config allows changing the branch, why don't you default the 3 questions on the install script. Is "duo" and "no" that important? I was stressed out by the questions when I first installed. Just a suggestion :)
Nathan Robinson
@nrobinson2000
Yeah I should probably make those use default values in the next update
Nathan Robinson
@nrobinson2000
I've made it so it defaults to the develop branch in the installation and it will no longer ask for the config during the installation.
Nathan Robinson
@nrobinson2000
If you want to log the installation to a file you could do:
bash <(curl -sL get.po-util.com) 2>&1 | tee po-install.log
Jeremy Ellis
@hpssjellis
That is useful.
Hey Nathan, any chance you can generate a po-util version number such as 0.8.18 in the badge somehow. Would be very useful as things change.
Jeremy Ellis
@hpssjellis
I also sent you a message on particle forum of a suggestion for your blank main.cpp
Nathan Robinson
@nrobinson2000
Jeremy Ellis
@hpssjellis
That's more fancy than I was thinking. If you can get it working great, but just text on your PO title screen would work as well.
Nathan Robinson
@nrobinson2000
Oh like a version number in po or po info? I'll see if I can do that.
Jeremy Ellis
@hpssjellis
image.png
Jeremy Ellis
@hpssjellis
image.png
Nathan: On cloud9 po-util generates a firmware.bin file in the main directory, but when I do po clean that file does not get deleted. Is this a bug? I just renamed it and then ran another build and it made another one.
Nathan Robinson
@nrobinson2000
It's not supposed to. It's for if you are building for multiple platforms and you want save a binary for each platform. po clean deletes the bin/ directory.
Nathan Robinson
@nrobinson2000
I've released 0.6.7 which displays the po-util version in po and po info. Support for Device OS v1.0.0 is added as well.
Jeremy Ellis
@hpssjellis
Nice. Well Done. I am getting better at using Cloud9 po and then downloading and using particle flash -usb file.bin much faster than cloud9 OTA, which was very unstable today.
Jeremy Ellis
@hpssjellis
does po config mesh-develop have to be done before po setup-mesh?
Nathan Robinson
@nrobinson2000
Yes
Jeremy Ellis
@hpssjellis
Quick question for my own bash files. Does the install script "bash <(curl -sL get.po-util.com)" exit gracefully if the po-util is already installed with the latest version or does it install from scratch every time you run it? I know I could just try it, but mine is now working nicely on Ubuntu and I don't want to wreck it.
Nathan Robinson
@nrobinson2000
It overwrites the po files
Jeremy Ellis
@hpssjellis
Ok. Am I ever getting very fast at working with po-util. I work on the cloud, but download the generated firmware to my computer to install using dfu. Takes seconds to test new firmware, compared to OTA which at school took up to 14 minutes and would not tell me if it was successful. Very impressed.
Jeremy Ellis
@hpssjellis
Just installed version 0.6.7 and it works well.
Nathan Robinson
@nrobinson2000
I've released 0.6.8 which adds support for the official Particle project structure and building with the Particle Workbench makefile. https://github.com/nrobinson2000/po/releases/tag/0.6.8
Thorsten von Eicken
@tve
I'm having a minor issue compiling and flashing a xenon. po xenon run flash-user fails in the compilation, but po xenon run compile-user succeeds.
/home/tve/.po-util/bin/gcc-arm-embedded/gcc-arm-none-eabi-5_3-2016q1/bin/../lib/gcc/arm-none-eabi/5.
3.1/../../../../arm-none-eabi/bin/ld: cannot open linker script file module_user_memory.ld: No such
file or directory
Nathan Robinson
@nrobinson2000
What about po xenon flash-beta ?
Thorsten von Eicken
@tve
tve@soumak /h/s/g/p/gps-test> po xenon flash-beta

          ______    ______
         /      \  /      \    Building firmware...
        /██████  |/██████  |
        ██ |  ██ |██ |  ██ |   Build Parameters:
        ██ |__██ |██ \__██ |     xenon
        ██    ██/ ██    ██/      gps-test
        ███████/   ██████/
        ██ |
        ██ |
        ██/  po xenon build gps-test

/home/tve/.po-util/bin/gcc-arm-embedded/gcc-arm-none-eabi-5_3-2016q1/bin/../lib/gcc/arm-none-eabi/5.3.1/../../../../arm-none-eabi/bin/ld: cannot open linker script file module_user_memory.ld: No such
file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [../../../build/module.mk:235: /home/src/goobies/particle/gps-test/target/gps-test.elf] Error 1
make[1]: *** [../build/recurse.mk:12: modules/xenon/user-part] Error 2
make: *** [/home/tve/.po-util/src/particle.mk:46: flash-user] Error 2

Building firmware failed! DFU closed.


No Particle Devices in DFU mode found!
same linker error
Nathan Robinson
@nrobinson2000
Can you try cleaning? po xenon clean-beta
Thorsten von Eicken
@tve
same issue
tve@soumak /h/s/g/p/gps-test> po xenon clean-beta

Cleaning firmware...
Sucessfully cleaned.

tve@soumak /h/s/g/p/gps-test> po xenon flash-beta

          ______    ______
         /      \  /      \    Building firmware...
        /██████  |/██████  |
        ██ |  ██ |██ |  ██ |   Build Parameters:
        ██ |__██ |██ \__██ |     xenon
        ██    ██/ ██    ██/      gps-test
        ███████/   ██████/
        ██ |
        ██ |
        ██/  po xenon build gps-test

/home/tve/.po-util/bin/gcc-arm-embedded/gcc-arm-none-eabi-5_3-2016q1/bin/../lib/gcc/arm-none-eabi/5.3.1/../../../../arm-none-eabi/bin/ld: cannot open linker script file module_user_memory.ld: No such
file or directory
collect2: error: ld returned 1 exit status
make[2]: *** [../../../build/module.mk:235: /home/src/goobies/particle/gps-test/target/gps-test.elf] Error 1
make[1]: *** [../build/recurse.mk:12: modules/xenon/user-part] Error 2
make: *** [/home/tve/.po-util/src/particle.mk:46: flash-user] Error 2

Building firmware failed! DFU closed.


No Particle Devices in DFU mode found!
Thorsten von Eicken
@tve
In po-common, line 1776, there is no "$1" unlike on line 1754 (store_build_parameters-beta "$1"), that doesn't solve it though
Thorsten von Eicken
@tve
It looks to me like adding a prebuild prereq to the program-dfu target in the particle build/module.mk solves the linking issue. Line 122 :
program-dfu: prebuild $(MAKE_DEPENDENCIES) $(TARGET_BASE).dfu
should probablyu also have a postbuild prereq...
the all target used by compile-beta says:
all: prebuild $(MAKE_DEPENDENCIES) $(TARGET) postbuild
and gittter.im is having a hiccup...
The reason UI have to explicitly run po dfu open -d /dev/ttyACM0 is:
tve@soumak ~> dfu-util -l
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

tve@soumak ~>
Nathan Robinson
@nrobinson2000
Which version of gcc-arm are you using?
arm-none-eabi-gcc --version
Thorsten von Eicken
@tve
I removed all globally installed arm-none-eabi-gcc
tve@soumak ~> ~/.po-util/bin/gcc-arm-embedded/gcc-arm-none-eabi-5_3-2016q1/bin/arm-none-eabi-gcc --version
arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.3.1 20160307 (release) [ARM/embedded-5-branch revision 234589]
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
(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.