lps33hw sensor driver
Hi All, I was trying to figure out how to organize the work to add support to MyNewT for the new MEMS sensors produced by STMicroelectronics and I came across the lps33hw driver (hw / driver / sensors / lps33hw) which actually also supports the part number LPS22HB, in fact both devices have - the same Who am I - same functionalities - same register map and bitmap these devices differ only by the case type because LPS33HW is for water proof application while LPS22HB is for generic usage. Would it be possible to indicate in the documentation that the lps33hw driver into the distro supports both LPS33HW and LPS22HB devices (?) Best Regards, Mario
Re: newt test suite for a bsp port
Hi Inderpal, On Fri, Apr 12, 2019 at 02:38:27PM +0530, inderpal singh wrote: > Hi There, > > How can I run existing test suite for particular BSP instead of native. > > #newt test all > instead of native how can I run this on my target. There are two kinds of Mynewt unit tests: 1. Self tests. 2. Hosted test. Self tests run in the simulator via "newt test". Hosted tests run on actual hardware. These need to be built into a Mynewt app which gets loaded onto a device. Hosted tests are more challenging to use than self tests because: 1. The system does not reset itself between each unit test. Your unit tests need to ensure a clean state when they are set up. 2. You need some extra tooling to retrieve test results from the device. 3. The tests must run in a constrained embedded environment. `apps/testbench` is an example of an app that runs hosted tests. You use the `newtmgr` tool (http://mynewt.apache.org/latest/newtmgr/index.html) to run tests and collect test results. To run all hosted tests: newtmgr run test all To read results: newtmgr log show testlog A few notes: * You will need to specify a connection profile or connection string on the command line; see the newtmgr documentation. * The `log show` command needs to be executed many times to collect all the test results. I recommend starting with this testbench application. Once you get it running, you can add additional tests. Chris
newt test suite for a bsp port
Hi There, How can I run existing test suite for particular BSP instead of native. #newt test all instead of native how can I run this on my target. Thanks & regards, Inderpal
Re: switching to mcuboot
Hi again, On Fri, 12 Apr 2019 at 11:00, Łukasz Rymanowski < lukasz.rymanow...@codecoup.pl> wrote: > Hi Szymon, > > Like the idea - I think we also need newt tool to point to some mcuboot > version right? > Ah nevermind, all is in the mentioned PR :) > > Best > Łukasz > > Łukasz > On Fri, 12 Apr 2019 at 10:50, Szymon Janc wrote: > >> Hi, >> >> As discussed on several occasions we want to move away from bootutils and >> start using mcuboot project directly. >> >> PR implementing this is here >> https://github.com/apache/mynewt-core/pull/1763 >> It is not yet ready to be merged due to some issues with tests on mcuboot >> side >> >> Open points for this PR which I'd like to get some feedback on: >> - fixing (or removing?) tests that are executed with newt test all >> - should newt create-image default to new image header version (-2 >> option) >> once we switch to mcuboot? >> - which mcuboot version should core track? Since it is external project I >> suggest that master >> tracks 1-latest and when we release we stick to latest released version >> at that time (eg core 1.7.0 would depend on mcuboot 1.3.0, 1.8 on 1.4.0 if >> released etc) >> >> >> -- >> pozdrawiam >> Szymon K. Janc >> >
Re: switching to mcuboot
Hi Szymon, Like the idea - I think we also need newt tool to point to some mcuboot version right? Best Łukasz On Fri, 12 Apr 2019 at 10:50, Szymon Janc wrote: > Hi, > > As discussed on several occasions we want to move away from bootutils and > start using mcuboot project directly. > > PR implementing this is here > https://github.com/apache/mynewt-core/pull/1763 > It is not yet ready to be merged due to some issues with tests on mcuboot > side > > Open points for this PR which I'd like to get some feedback on: > - fixing (or removing?) tests that are executed with newt test all > - should newt create-image default to new image header version (-2 option) > once we switch to mcuboot? > - which mcuboot version should core track? Since it is external project I > suggest that master > tracks 1-latest and when we release we stick to latest released version > at that time (eg core 1.7.0 would depend on mcuboot 1.3.0, 1.8 on 1.4.0 if > released etc) > > > -- > pozdrawiam > Szymon K. Janc >
switching to mcuboot
Hi, As discussed on several occasions we want to move away from bootutils and start using mcuboot project directly. PR implementing this is here https://github.com/apache/mynewt-core/pull/1763 It is not yet ready to be merged due to some issues with tests on mcuboot side Open points for this PR which I'd like to get some feedback on: - fixing (or removing?) tests that are executed with newt test all - should newt create-image default to new image header version (-2 option) once we switch to mcuboot? - which mcuboot version should core track? Since it is external project I suggest that master tracks 1-latest and when we release we stick to latest released version at that time (eg core 1.7.0 would depend on mcuboot 1.3.0, 1.8 on 1.4.0 if released etc) -- pozdrawiam Szymon K. Janc
Re: Removing transient packages from core
Hi, Yes, I've started working on that On Wed, 10 Apr 2019 at 16:55, Sterling Hughes < sterling.hughes.pub...@gmail.com> wrote: > Hi Szymon, > > Great, while you are looking at this, it would be excellent if you could > also do: > > https://github.com/apache/mynewt-core/issues/1695 > > It would be good to get time on these changes to stabilize prior to next > release. > > Sterling > > On 10 Apr 2019, at 6:17, Szymon Janc wrote: > > > Hi, > > > > Just a heads up that since we are right after release it is good time > > to > > start doing housekeeping :) > > > > PR removing transient packages is pending review: > > https://github.com/apache/mynewt-core/pull/1757 > > > > Make sure to update your targets when this gets merged! > > > > -- > > pozdrawiam > > Szymon K. Janc > -- pozdrawiam Szymon K. Janc
