Re: Override pin settings

2017-01-13 Thread David G. Simmons
Hi Chris, > On Jan 13, 2017, at 12:59 PM, Christopher Collins wrote: > > The last two entries should look like this: > >UART_0_PIN_TX: 23 >UART_0_PIN_RX: 24 > > I think this will be a common mistake, so we should look at making newt > report an error here. Thanks for clarifying tha

Re: Override pin settings

2017-01-13 Thread Christopher Collins
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

2017-01-13 Thread David G. Simmons
> 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 change > those UART pin o

Re: Override pin settings

2017-01-13 Thread Christopher Collins
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 > UART_0_PIN