[jira] [Commented] (MYNEWT-782) Atmel SAMD21 i2c probing
[ https://issues.apache.org/jira/browse/MYNEWT-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048695#comment-16048695 ] Marko Kiiskila commented on MYNEWT-782: --- That is possible. Should be investigated. > Atmel SAMD21 i2c probing > > > Key: MYNEWT-782 > URL: https://issues.apache.org/jira/browse/MYNEWT-782 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila > > I have 2 test i2c devices. I can do 'i2c_scan' on either, but will discover > the device only once. > On subsequent runs the device does not report being present. Should > investigate if this is because a) the device itself refuses to respond or b) > hal i2c driver on SAMD21 is faulty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MYNEWT-782) Atmel SAMD21 i2c probing
Marko Kiiskila created MYNEWT-782: - Summary: Atmel SAMD21 i2c probing Key: MYNEWT-782 URL: https://issues.apache.org/jira/browse/MYNEWT-782 Project: Mynewt Issue Type: Bug Security Level: Public (Viewable by anyone) Reporter: Marko Kiiskila I have 2 test i2c devices. I can do 'i2c_scan' on either, but will discover the device only once. On subsequent runs the device does not report being present. Should investigate if this is because a) the device itself refuses to respond or b) hal i2c driver on SAMD21 is faulty. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-529) i2c bus scanner
[
https://issues.apache.org/jira/browse/MYNEWT-529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko Kiiskila resolved MYNEWT-529.
---
Resolution: Fixed
Now available as separate package test/i2c_scan
> i2c bus scanner
> ---
>
> Key: MYNEWT-529
> URL: https://issues.apache.org/jira/browse/MYNEWT-529
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: HAL
>Reporter: Marko Kiiskila
>Assignee: Marko Kiiskila
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> Bring in Kevin's i2c bus scanner, probably in form of separate package.
> test/i2c_tools maybe?
> static int
> shell_i2cscan_cmd(int argc, char **argv)
> {
>uint8_t addr;
>int32_t timeout = OS_TICKS_PER_SEC / 10;
>uint8_t dev_count = 0;
>console_printf("Scanning I2C bus 0\n"
> " 0 1 2 3 4 5 6 7 8 9 a b c de f\n"
> "00: ");
>/* Scan all valid I2C addresses (0x03..0x77) */
>for (addr = 0x08; addr < 0x78; addr++) {
>int rc = hal_i2c_master_probe(0, addr, timeout);
>/* Print addr header every 16 bytes */
>if (!(addr % 16)) {
> console_printf("\n%02x: ", addr);
>}
>/* Display the addr if a response was received */
>if (!rc) {
>console_printf("%02x ", addr);
>dev_count++;
>} else {
>console_printf("-- ");
>}
>}
>console_printf("\nFound %u devices on I2C bus 0\n", dev_count);
>return 0;
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-529) i2c bus scanner
[
https://issues.apache.org/jira/browse/MYNEWT-529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048588#comment-16048588
]
ASF subversion and git services commented on MYNEWT-529:
Commit 1839134dc34a9797d1f50733351e3d32a96fcea0 in incubator-mynewt-core's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=1839134 ]
MYNEWT-529 - move i2c_scan to a separate package.
> i2c bus scanner
> ---
>
> Key: MYNEWT-529
> URL: https://issues.apache.org/jira/browse/MYNEWT-529
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: HAL
>Reporter: Marko Kiiskila
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Bring in Kevin's i2c bus scanner, probably in form of separate package.
> test/i2c_tools maybe?
> static int
> shell_i2cscan_cmd(int argc, char **argv)
> {
>uint8_t addr;
>int32_t timeout = OS_TICKS_PER_SEC / 10;
>uint8_t dev_count = 0;
>console_printf("Scanning I2C bus 0\n"
> " 0 1 2 3 4 5 6 7 8 9 a b c de f\n"
> "00: ");
>/* Scan all valid I2C addresses (0x03..0x77) */
>for (addr = 0x08; addr < 0x78; addr++) {
>int rc = hal_i2c_master_probe(0, addr, timeout);
>/* Print addr header every 16 bytes */
>if (!(addr % 16)) {
> console_printf("\n%02x: ", addr);
>}
>/* Display the addr if a response was received */
>if (!rc) {
>console_printf("%02x ", addr);
>dev_count++;
>} else {
>console_printf("-- ");
>}
>}
>console_printf("\nFound %u devices on I2C bus 0\n", dev_count);
>return 0;
> }
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (MYNEWT-699) recreate linker files which show how to build olimex bsp to run from RAM
[ https://issues.apache.org/jira/browse/MYNEWT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila resolved MYNEWT-699. --- Resolution: Fixed Added these files back. Updated the run_from_loader.ld to look exactly like the currently active script. > recreate linker files which show how to build olimex bsp to run from RAM > > > Key: MYNEWT-699 > URL: https://issues.apache.org/jira/browse/MYNEWT-699 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > I removed them as unused, without realizing that our tutorials talk refer > them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-699) recreate linker files which show how to build olimex bsp to run from RAM
[ https://issues.apache.org/jira/browse/MYNEWT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048575#comment-16048575 ] ASF subversion and git services commented on MYNEWT-699: Commit 6a896c0cd2127a9b4def97f940fdaadf53d23445 in incubator-mynewt-core's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6a896c0 ] MYNEWT-699; re-add sample linker scripts to Olimex BSP. > recreate linker files which show how to build olimex bsp to run from RAM > > > Key: MYNEWT-699 > URL: https://issues.apache.org/jira/browse/MYNEWT-699 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > I removed them as unused, without realizing that our tutorials talk refer > them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-699) recreate linker files which show how to build olimex bsp to run from RAM
[ https://issues.apache.org/jira/browse/MYNEWT-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048576#comment-16048576 ] ASF subversion and git services commented on MYNEWT-699: Commit 596c007dc79bd64c721bc4d2a945024eba08c4f0 in incubator-mynewt-core's branch refs/heads/master from [~marko] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=596c007 ] Merge pull request #334 from mkiiskila/olimex_xtra_ld MYNEWT-699; re-add sample linker scripts to Olimex BSP. > recreate linker files which show how to build olimex bsp to run from RAM > > > Key: MYNEWT-699 > URL: https://issues.apache.org/jira/browse/MYNEWT-699 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > I removed them as unused, without realizing that our tutorials talk refer > them. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-681: Component/s: BSP > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: BSP >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-744) SensorAPI: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-744: Component/s: Sensor Framework Drivers > SensorAPI: improvements > --- > > Key: MYNEWT-744 > URL: https://issues.apache.org/jira/browse/MYNEWT-744 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Drivers, Sensor Framework >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > - Change data structure to SLIST instead of TAILQ so that it can get > initialized statically. This is needed so that sysinit could be used for > initializing the sensors. > - Remove dummy functions in the bsp and add the sensor device initialization > functions instead. > - Adding syscfg based configuration for onboard Vs offboard sensors > - Adding sensor creator package for creating external sensor devices if they > are not on the board itself. This is just for convenience sake. The right way > to do this would be from the bsp. As a result, removed sensor device creation > from nrf52dk and nrf52840pdk bsps. > - Add sensor interface struct so that it can get used by the individual > drivers so that we can talk to multiple sensors using the same driver using > same or different interfaces. > - For TSL2561, apart from the above changes, various fixes were made: > 1. Making a few changes to this driver along with sensor_itf changes > 2. Gain, integration time and enabled flag was a global instead of > reading every time gain is set or integration time is set. Changing it so > that we read the timing register before setting either gain or integration > time. > 3. Also changing a few functions in the driver to handle errors more > gracefully. Changing shell to work with new functions. > 4. Making changes so that it goes in synch with the drivers. > 5. Removing delays from the read function. the poller should be set > according to the other config values being set so that the sensor is read at > the correct interval. > - Add a mask field to the sensor structure so that differentiating between > supported Vs configured sensors is possible > - Change the sensor_mgr_match_bytype() function to check w.r.t mask and make > it a public API. > - Adding config variable for mask for different drivers in their respective > structures. > - Adding an API to set the sensor types based on the mask. > - Moving config_sensor() out of the app into the creator package and the bsp. > Objective is to show how a developer would initialize and configure the > sensor in the bsp which is normally the practice. > - Changing sensor_shell command "list" to show only configured types. > - sensor_shell cmd "type" shows supported types set by the driver. > - In the sensor_oic source file changing code to check type only while > allocating resources. > - Changing device name in the sensors_test app to be "sensy" instead of "pi" > - For the LSM303DLHC driver the address field in the "sensor_itf" structure > is not enough since it talks to the sensor using two addresses: one for > accelerometer and one for magnetometer. The best way to deal with this is to > make the addresses config variables in the sensor driver structure. For any > such sensor devices which have multiple addresses, a similar approach should > be followed. > - Have changed the drivers to work with all the fixes mentioned above. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-739) sensor_test app: improvements
[ https://issues.apache.org/jira/browse/MYNEWT-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-739: Component/s: Sensor Framework > sensor_test app: improvements > - > > Key: MYNEWT-739 > URL: https://issues.apache.org/jira/browse/MYNEWT-739 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Drivers, Sensor Framework > Environment: nRF52dk with Adafruit BNO055 sensor and Minicom >Reporter: Sheela >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > This ticket will take care of any improvements we want for the app: > 1. Built code from the tip to include Sensors. Connected Adafruit BNO055 via > I2C interface to nRF52dk. Modified Syscfg to "nrf52_sensor > syscfg=BNO055_I2CBUS=0:I2C_0=1" for the BNO055 sensor. > Using sensors_test, issued 'sensor list' command which yielded "sensor dev = > color0, type = 0x8000 " as result. > Noticed that in syscfg the "TCS34725_PRESENT" was also set to '1' by default > and 'sensor list' automatically shows only that sensor. > sensor list should show all the sensors that are configured. > In the app tcs34725_config() was failing which was causing the sensor list to > not get populated. > 2. Remove config, gpio toggle stats, gpio toggle logs from the app. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-777: Component/s: Sensor Framework Drivers > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) > Components: Drivers, Sensor Framework >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-779: Component/s: Sensor Framework Drivers > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Drivers, Sensor Framework >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-780: Component/s: Sensor Framework Drivers > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Drivers, Sensor Framework >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-781: Component/s: Drivers > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: Drivers >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MYNEWT-631) SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro
[ https://issues.apache.org/jira/browse/MYNEWT-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane updated MYNEWT-631: Component/s: drivers > SensorAPI: BNO055 Sensor not working with Arduino M0/Zero Pro > - > > Key: MYNEWT-631 > URL: https://issues.apache.org/jira/browse/MYNEWT-631 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) > Components: drivers >Affects Versions: v1_0_0_beta2 >Reporter: Vipul Rahane >Assignee: Vipul Rahane >Priority: Minor > Attachments: bno055_capture.png > > > While trying out different sensors with the SensorsAPI, a bug was found with > the Arduino Zero Pro/M0 Pro. BNO055 does not work with it. Attaching the > timing capture while reading the CHIP_ID of the sensor. > Most probably this is due to clock stretching, this can be observed in the > capture. The sensor works fine with nRF52DK. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-780. - Resolution: Fixed > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-779. - Resolution: Fixed > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-648) "newt test net/oic" fails when compiling with clang
[ https://issues.apache.org/jira/browse/MYNEWT-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila resolved MYNEWT-648. --- Resolution: Fixed This has been fixed as part of earlier commits. > "newt test net/oic" fails when compiling with clang > --- > > Key: MYNEWT-648 > URL: https://issues.apache.org/jira/browse/MYNEWT-648 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > $ newt test net/oic > Testing package net/oic/test > Compiling encoding/cborattr/src/cborattr.c > Compiling encoding/tinycbor/src/cborerrorstrings.c > > Compiling net/oic/src/api/oc_server_api.c > In file included from net/oic/src/api/oc_buffer.c:23: > In file included from net/oic/src/messaging/coap/engine.h:38: > In file included from net/oic/src/messaging/coap/observe.h:45: > net/oic/include/oic/oc_ri.h:126:3: error: redefinition of typedef > 'oc_resource_t' is a C11 feature [-Werror,-Wtypedef-redefinition] > } oc_resource_t; > ^ > net/oic/include/oic/oc_ri.h:98:28: note: previous definition is here > typedef struct oc_resource oc_resource_t; >^ > net/oic/include/oic/oc_ri.h:152:28: error: redefinition of typedef > 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition] > typedef struct coap_packet coap_packet_t; >^ > net/oic/src/messaging/coap/coap.h:227:3: note: previous definition is here > } coap_packet_t; > ^ > In file included from net/oic/src/api/oc_buffer.c:23: > In file included from net/oic/src/messaging/coap/engine.h:39: > In file included from net/oic/src/messaging/coap/separate.h:46: > net/oic/src/messaging/coap/oc_coap.h:30:3: error: redefinition of typedef > 'oc_separate_response_t' is a C11 feature [-Werror,-Wtypedef-redefinition] > } oc_separate_response_t; > ^ > net/oic/include/oic/oc_ri.h:64:37: note: previous definition is here > typedef struct oc_separate_response oc_separate_response_t; > ^ > In file included from net/oic/src/api/oc_buffer.c:23: > In file included from net/oic/src/messaging/coap/engine.h:39: > In file included from net/oic/src/messaging/coap/separate.h:46: > net/oic/src/messaging/coap/oc_coap.h:37:3: error: redefinition of typedef > 'oc_response_buffer_t' is a C11 feature [-Werror,-Wtypedef-redefinition] > } oc_response_buffer_t; > ^ > net/oic/include/oic/oc_ri.h:66:35: note: previous definition is here > typedef struct oc_response_buffer oc_response_buffer_t; > ^ > In file included from net/oic/src/api/oc_buffer.c:23: > In file included from net/oic/src/messaging/coap/engine.h:39: > net/oic/src/messaging/coap/separate.h:67:28: error: redefinition of typedef > 'coap_packet_t' is a C11 feature [-Werror,-Wtypedef-redefinition] > typedef struct coap_packet coap_packet_t; >^ > net/oic/include/oic/oc_ri.h:152:28: note: previous definition is here > typedef struct coap_packet coap_packet_t; >^ > 5 errors generated. > Error: Test failure(s): > Passed tests: [] > Failed tests: [net/oic/test] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-644) newt build's hunt for project.yml fails to find it when starting in sub-dir
[ https://issues.apache.org/jira/browse/MYNEWT-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marko Kiiskila resolved MYNEWT-644. --- Resolution: Cannot Reproduce This does not appear to be an issue anymore; I cannot reproduce it now. Closing it. > newt build's hunt for project.yml fails to find it when starting in sub-dir > --- > > Key: MYNEWT-644 > URL: https://issues.apache.org/jira/browse/MYNEWT-644 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Affects Versions: v1_0_0_rel >Reporter: Marko Kiiskila >Assignee: Marko Kiiskila > Fix For: v1_1_0_rel > > > This is what it looks like: > Z:\marko\src8\incubator-mynewt-blinky\repos>newt -lDEBUG build boot_bbc > 2017/02/27 21:01:51.450 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.451 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.452 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.453 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.454 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.455 [DEBUG] Searching for project file ./project.yml > 2017/02/27 21:01:51.456 [DEBUG] Searching for project file ./project.yml -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048469#comment-16048469 ] ASF subversion and git services commented on MYNEWT-780: Commit 3e044fc39584b91d48114d9132bbad0eb106592f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3e044fc ] Merge pull request #331 from vrahane/MYNEWT-780 MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048464#comment-16048464 ] ASF subversion and git services commented on MYNEWT-779: Commit 6d63e997396ad92dee3e03fb49cdb98196ef2c78 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6d63e99 ] Merge pull request #332 from vrahane/MYNEWT-779 MYNEWT-779 tcs34725 driver: remove os_time_delay() > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048465#comment-16048465 ] ASF subversion and git services commented on MYNEWT-779: Commit 6d63e997396ad92dee3e03fb49cdb98196ef2c78 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=6d63e99 ] Merge pull request #332 from vrahane/MYNEWT-779 MYNEWT-779 tcs34725 driver: remove os_time_delay() > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048466#comment-16048466 ] ASF subversion and git services commented on MYNEWT-780: Commit 43c2103373045cd0bac1e597cfbdf66d2c4ec1d3 in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=43c2103 ] MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048467#comment-16048467 ] ASF subversion and git services commented on MYNEWT-780: Commit 08c184989ce45aa34d1316a259517c8252ca3a3a in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=08c1849 ] MYNEWT-780 TCS34725 exposing address cfg for shell > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-780) Sensor device shells: add addresses as syscfg to populate g_sensor_itf
[ https://issues.apache.org/jira/browse/MYNEWT-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048468#comment-16048468 ] ASF subversion and git services commented on MYNEWT-780: Commit 3e044fc39584b91d48114d9132bbad0eb106592f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3e044fc ] Merge pull request #331 from vrahane/MYNEWT-780 MYNEWT-780 Sensor driver shells: expose ADDR syscf > Sensor device shells: add addresses as syscfg to populate g_sensor_itf > -- > > Key: MYNEWT-780 > URL: https://issues.apache.org/jira/browse/MYNEWT-780 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Sensor device shells: add addresses as syscfg to populate g_sensor_itf -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-779) SensorAPI: tcs34725 driver: remove os_time_delay()
[ https://issues.apache.org/jira/browse/MYNEWT-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048463#comment-16048463 ] ASF subversion and git services commented on MYNEWT-779: Commit fdd2557773886fb9002c3f125a5dd9a14982623d in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=fdd2557 ] MYNEWT-779 tcs34725 driver: remove os_time_delay() - Removing os_time_delay() from driver and moving it to shell for using it with shell. - Sensor framework polling timer should be used for reading instead of os_time_delay(). > SensorAPI: tcs34725 driver: remove os_time_delay() > -- > > Key: MYNEWT-779 > URL: https://issues.apache.org/jira/browse/MYNEWT-779 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Remove os_time_delay() from driver and move it to shell for using it with > shell specifically as there is already a poller for the sensor framework and > this kind of messes up the poll rate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko Kiiskila resolved MYNEWT-720.
---
Resolution: Fixed
Code merged.
Now there is 'newt resign-image' command available.
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marko Kiiskila updated MYNEWT-720:
--
Fix Version/s: v1_1_0_rel
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
> Fix For: v1_1_0_rel
>
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048375#comment-16048375
]
ASF subversion and git services commented on MYNEWT-720:
Commit cd248f806a8a1325caea1f55c2d8f5314035 in incubator-mynewt-newt's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=cd248f8 ]
Merge pull request #68 from mkiiskila/re-sign
MYNEWT-720; add 'newt resign-image' command.
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-720) Newt: manipulate image signatures
[
https://issues.apache.org/jira/browse/MYNEWT-720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048374#comment-16048374
]
ASF subversion and git services commented on MYNEWT-720:
Commit 25b3864b689cb1101dc280c9fc7a1a6c64df8a25 in incubator-mynewt-newt's
branch refs/heads/master from [~marko]
[ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-newt.git;h=25b3864 ]
MYNEWT-720; add 'newt resign-image' command.
> Newt: manipulate image signatures
> -
>
> Key: MYNEWT-720
> URL: https://issues.apache.org/jira/browse/MYNEWT-720
> Project: Mynewt
> Issue Type: New Feature
> Security Level: Public(Viewable by anyone)
> Components: Newt
>Affects Versions: v1_0_0_rel
>Reporter: Simon Ratner
>Assignee: Marko Kiiskila
>Priority: Minor
>
> Ability to manipulate image signatures should be independent of creating the
> image. Suggesting a new command:
> {noformat}
> newt sign-image
> {noformat}
> Useful operations:
> * strip a signature from an existing image,
> * sign an existing unsigned image,
> * re-sign an existing image with a different key.
> In all cases, the rest of the image besides the signature should remain
> byte-for-byte identical.
> Motivating use cases:
> * dev images are promoted to qa, prod; qa and prod keys are kept separate,
> but the promoted image should not be rebuilt from source, to eliminate any
> possibility that an untested configuration is deployed due to differences in
> build environment.
> * distinct keys for different customers, used to sign the same image.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048277#comment-16048277 ] ASF subversion and git services commented on MYNEWT-681: Commit 618f56a734808a7931f0626d9a8e401bd5cfc518 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=618f56a ] Merge pull request #318 from vrahane/MYNEWT-681 MYNEWT-681 rb-nano2 remove flash write protection in download scripts > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048276#comment-16048276 ] ASF subversion and git services commented on MYNEWT-681: Commit 618f56a734808a7931f0626d9a8e401bd5cfc518 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=618f56a ] Merge pull request #318 from vrahane/MYNEWT-681 MYNEWT-681 rb-nano2 remove flash write protection in download scripts > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048274#comment-16048274 ] ASF subversion and git services commented on MYNEWT-681: Commit 3a0fd9da5541ee381e2b672375a8775475902d7c in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=3a0fd9d ] MYNEWT-681 openocd script remove unused file > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048278#comment-16048278 ] ASF subversion and git services commented on MYNEWT-781: Commit 17060baba1c59df0d83b395c4c629a41a1a8c4b1 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=17060ba ] MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048280#comment-16048280 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048275#comment-16048275 ] ASF subversion and git services commented on MYNEWT-681: Commit d59f281f45e69855ea3630d65b6b2df55af54bf4 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=d59f281 ] MYNEWT-681 openocd script fix wrong indentation > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048281#comment-16048281 ] ASF subversion and git services commented on MYNEWT-781: Commit 89e6027a83dc1d38f41adc8ae1e7d41d56c00551 in incubator-mynewt-core's branch refs/heads/bluetooth5 from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=89e6027 ] Merge pull request #330 from vrahane/MYNEWT-781 MYNEWT-781 BNO055 Shell: throw error on no type > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-681) rb-nano2 remove flash write protection in download script
[ https://issues.apache.org/jira/browse/MYNEWT-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-681. - Resolution: Fixed > rb-nano2 remove flash write protection in download script > - > > Key: MYNEWT-681 > URL: https://issues.apache.org/jira/browse/MYNEWT-681 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Marko Kiiskila >Assignee: Vipul Rahane > Labels: rb-nano2 > Fix For: v1_1_0_rel > > > Red bear nano2 comes with flash write protected for bootloader area. We > should remove this protection before trying to update the flash contents. > This ticket addresses the following: > - Remove write protection before flash erase > - Adding an extra variable EXTRA_GDB_CMDS similar to the jlink script so that > gdb commands can be added easily to the download and debug scripts. > - Fix indentation in the script -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-781) BNO055 shell: throw error on read with no type
[ https://issues.apache.org/jira/browse/MYNEWT-781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-781. - Resolution: Fixed > BNO055 shell: throw error on read with no type > -- > > Key: MYNEWT-781 > URL: https://issues.apache.org/jira/browse/MYNEWT-781 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > BNO055 shell: throw error on read with no type -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vipul Rahane resolved MYNEWT-777. - Resolution: Fixed > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048221#comment-16048221 ] ASF subversion and git services commented on MYNEWT-777: Commit 9379a3d62513a53288f07bb91e7897a82ae1846f in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=9379a3d ] Merge pull request #325 from vrahane/MYNEWT-777 MYNEWT-777 SensorAPI: Use util/parse pkg instead of using sensor_shell_stol() > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-777) SensorAPI: Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers
[ https://issues.apache.org/jira/browse/MYNEWT-777?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048219#comment-16048219 ] ASF subversion and git services commented on MYNEWT-777: Commit b3dfb7c6729c092e4ea528fe1ca55ed5b829b8fc in incubator-mynewt-core's branch refs/heads/master from [~vrahane] [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=b3dfb7c ] MYNEWT-777 SensorAPI: Use util/parse pkg - Use util/parse package for parsing instead of using sensor_shell_stol() or parsing functions in individual drivers > SensorAPI: Use util/parse package for parsing instead of using > sensor_shell_stol() or parsing functions in individual drivers > - > > Key: MYNEWT-777 > URL: https://issues.apache.org/jira/browse/MYNEWT-777 > Project: Mynewt > Issue Type: Improvement > Security Level: Public(Viewable by anyone) >Reporter: Vipul Rahane >Assignee: Vipul Rahane > Fix For: v1_1_0_rel > > > Use util/parse package for parsing instead of using sensor_shell_stol(), also > change it for all the drivers. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-664) coredownload newtmgr command should indicate core size in first response
[ https://issues.apache.org/jira/browse/MYNEWT-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-664. Resolution: Fixed > coredownload newtmgr command should indicate core size in first response > > > Key: MYNEWT-664 > URL: https://issues.apache.org/jira/browse/MYNEWT-664 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Christopher Collins >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > (Pull request: https://github.com/apache/incubator-mynewt-core/pull/312) > This would be analogous to the "image upload", "file upload", and "file > download" commands. Each of these indicate the total number of bytes in the > first packet. > This change involves a backwards compatible modification to the NMP protocol. > Compatibility is maintained because this change only requires the addition > of a new field, not the modification or removal of existing fields. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (MYNEWT-752) Error in setting the "permanent" flag upon confirm with hash during image upgrade
[ https://issues.apache.org/jira/browse/MYNEWT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Collins resolved MYNEWT-752. Resolution: Fixed > Error in setting the "permanent" flag upon confirm with hash during image > upgrade > - > > Key: MYNEWT-752 > URL: https://issues.apache.org/jira/browse/MYNEWT-752 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > This is an issue seen during image upgrade. When doing a "confirm" with a > hash, newtmgr always marks the "permanent" flag for Slot 1 image to "true", > irrespective of which image the hash matches. > This works fine when we skip the "test" step during image upgrade and we > issue a "confirm" with a hash of the new image in Slot 1. > However, if we do the "test" step (when the new image is swapped into Slot > 0), and we then do a "confirm" with a hash of the new image and reboot, the > device marks the old image in Slot 1 as "permanent" and swaps it back to Slot > 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MYNEWT-752) Error in setting the "permanent" flag upon confirm with hash during image upgrade
[ https://issues.apache.org/jira/browse/MYNEWT-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16048185#comment-16048185 ] ASF subversion and git services commented on MYNEWT-752: Commit 572cfa1c3473d4a42cc726944b176b2a5c485692 in incubator-mynewt-core's branch refs/heads/master from ccollins476ad [ https://gitbox.apache.org/repos/asf?p=incubator-mynewt-core.git;h=572cfa1 ] Merge pull request #313 from ccollins476ad/img-test-perm MYNEWT-752 Allow confirm of tentative slot. > Error in setting the "permanent" flag upon confirm with hash during image > upgrade > - > > Key: MYNEWT-752 > URL: https://issues.apache.org/jira/browse/MYNEWT-752 > Project: Mynewt > Issue Type: Bug > Security Level: Public(Viewable by anyone) >Reporter: Aditi Hilbert >Assignee: Christopher Collins > Fix For: v1_1_0_rel > > > This is an issue seen during image upgrade. When doing a "confirm" with a > hash, newtmgr always marks the "permanent" flag for Slot 1 image to "true", > irrespective of which image the hash matches. > This works fine when we skip the "test" step during image upgrade and we > issue a "confirm" with a hash of the new image in Slot 1. > However, if we do the "test" step (when the new image is swapped into Slot > 0), and we then do a "confirm" with a hash of the new image and reboot, the > device marks the old image in Slot 1 as "permanent" and swaps it back to Slot > 0. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
