Re: Single Bank firmware update (ie nordic vendor style dfu)

On Fri, Jan 13, 2017 at 04:38:25PM -0700, Jacob Rosenthal wrote: > Ah, I expected gdb of optimized split code to be a nightmare and hadnt > tried yet. > newtmgr has never crashed.. it just hangs forever > > I cant get the SOFT anymore now. hrmmm Just hanging out here.. > (gdb) where > #0

Re: Supporting multiple filesystems and "block" devices

On Fri, Jan 13, 2017 at 08:29:33PM -0200, Fabio Utzig wrote: > Yes, I was expecting it! So I had 3 options in mind: > > Option 1 - Use a "drive" name as was implemented. Btw, it's not limited > to single letter drive names! Sure if someone really likes DOS, they > could use A:, B:, etc. This

Re: Supporting multiple filesystems and "block" devices

> I'm sure you anticipated this comment :). Seeing a ':' in a path brings > back horrible memories for me. I am not sure if this is just an > aesthetic judgment, or if the "UNIX way" would actually be better. If > it's just an asthetic thing, then I'll get over it, but I can't help but > think

Re: Supporting multiple filesystems and "block" devices

+1 on UNIX paths. I have PTSD from DOS paths. :-) dg > On Jan 13, 2017, at 5:07 PM, Christopher Collins wrote: > > Hi Fabio, > > Sounds great. I only have one comment: > > On Fri, Jan 13, 2017 at 03:09:48PM -0200, Fabio Utzig wrote: >>> All the fs_* functions where

Re: [RFC] Refactor UUID handling in Nimble

Hi Andrzej, That all sounds good to me. Thanks, Chris On Fri, Jan 13, 2017 at 02:58:19PM +0100, Andrzej Kaczmarek wrote: > Hi, > > I've refactored Nimble code to use dedicated type for UUID handling instead > of generic byte-array. Full diff is available here (it is split into > several

Re: Supporting multiple filesystems and "block" devices

Hi Fabio, Sounds great. I only have one comment: On Fri, Jan 13, 2017 at 03:09:48PM -0200, Fabio Utzig wrote: > > All the fs_* functions where updated to support multiple disks. To > > access a file/dir now will required adding the name of the disk as a > > prefix like this: > > > > rc =

Re: Override pin settings

On Fri, Jan 13, 2017 at 11:35:13AM -0500, David G. Simmons wrote: > Here's the entire syscfg.yml file: > > ### Package: targets/air_q > > syscfg.vals: > OPENOCD_DEBUG: 1 > # Enable the shell task. > SHELL_TASK: 1 > STATS_CLI: 1 > > CONSOLE_TICKS: 1 > CONSOLE_PROMPT: 1 >

Re: Override pin settings

> On Jan 13, 2017, at 11:31 AM, Christopher Collins wrote: > > From your email, it looks like the target's syscfg.yml is redefining > existing settings, which should cause newt to raise an error. I'll look > into this error reporting issue, but in the meantime, I would

Re: Override pin settings

Hi David, On Fri, Jan 13, 2017 at 09:52:35AM -0500, David G. Simmons wrote: > Before I file a bug in Jira on this, I thought I'd ask if this is expected > behavior: > > From my project's syscfg.yml: > UART_0_PIN_TX: > description: 'New Pin Assignment' > value: 23 >

[RFC] Refactor UUID handling in Nimble

Hi, I've refactored Nimble code to use dedicated type for UUID handling instead of generic byte-array. Full diff is available here (it is split into several patches for now to separate changes in stack and apps): https://github.com/andrzej-kaczmarek/incubator-mynewt-core/c

Supporting multiple filesystems and "block" devices

Hello, I've been working on patch that adds support for accessing multiple devices and filesystems on Mynewt (overcoming the current single FS and "hardcoded" block device per driver). The PR is available here: https://github.com/apache/incubator-mynewt-core/pull/158 This PR is completely

Re: [RFC] nimble/l2cap: Add LE L2CAP COC API

Hi Chris, On 13 January 2017 at 03:19, Christopher Collins wrote: > Hi Łukasz, > > It sounds good to me. I just have a few questions: > > On Thu, Jan 12, 2017 at 09:41:49PM +0100, Łukasz Rymanowski wrote: > > Outgoing connection: > > 1. *chan =