Hello all,
This thread is for any and all discussion regarding the release of
apache-mynewt-1.0.0-b1-incubating-rc1. All feedback is welcome.
Thanks,
Chris
Hello all,
I am pleased to be calling this vote for the source release of Apache
Mynewt 1.0.0, beta 1.
Apache Mynewt is a community-driven, permissively licensed open source
initiative for constrained, embedded applications. Mynewt provides a
real-time operating system, flash file system,
Hello,
Recently while setting up the multiple connection demo, I found weird issues
with some of the boards which causes the flash on the boards to get locked up,
I know the symptoms but I am not sure about what causes it:
How do you know it’s locked up ?
Do you have any other devices connected to your nRF (electronically, not
BLE) and are actively trying to send data to the nRF?
If so, detach them and try again.
In one repeatable case I've found it impossible to connect to an nRF51
using SWD via the J-Link when another MCU was communicating using
The nRF51 also (strangely!) has a non standard SWD interface. It's the
first time I've come across that, and I'm not sure what the thinking
behind multiplexing RST with the SWD pins was (extremely low pin count
devices?), but it breaks the normal behaviour of SWD on ARM Cortex M and
you need
I generally put a factory reset pin in projects that I check very early
on, which has saved my butt more than once, though it isn't fool proof.
It's just nice to have an early stage option to go back to a known state
when devices are in the field or even during development (and you can
NRF52DK. I managed to get it reset. Timing is hard to get perfect. The 'Reset'
button is ignored.
I think this might point to the need for an os_suspend() or an os_stop()
function.
dg
> On Nov 22, 2016, at 12:13 PM, marko kiiskila wrote:
>
> Usually I have a button. But
Usually I have a button. But I have had to use jumper wires also :)
What board are you using?
> On Nov 22, 2016, at 9:07 AM, David G. Simmons wrote:
>
> How are you keeping the board in reset? The only method I've found is to
> power the board off, and so far, my timing has
How are you keeping the board in reset? The only method I've found is to power
the board off, and so far, my timing has not paid off on that front.
dg
> On Nov 22, 2016, at 12:04 PM, marko kiiskila wrote:
>
> Hi,
>
> my trick with this is by keeping the board in reset just
Hi Julian,
fantastic. I pulled in these changes. One note though; I noticed 3 files were
missing
license info; hw/bsp/ci40/uhi32.ld, and hw/mcu/mips/danube/src/gic.[ch]. Would
you
able to create another pull request to fix that?
Also, are there any gotchas in setting up cross-compilation
Well, it sort of avoids your question but when I had an nRF board that
ignored my recovery attempts this worked:
https://devzone.nordicsemi.com/blogs/16/recover-the-nrf51-when-nrjprog-and-nrfgo-studio-co/
Although it looks like you can't even connect which seems bad.
On 22 Nov 2016 15:18,
11 matches
Mail list logo