Dev probably isn't the ideal place to post this, but I'm filing it here
in case the request is useful to other people in the future.
I'm trying to determine how the bootloader functions with image
management, and what functionality is currently in place, and I was
hoping someone could clarify is whether flashing only the bootloader (on
the nRF51822 in this case) is enough to allow for firmware updates over
serial?
I've tried the following with a custom BSP that I've confirmed USB
Serial works for with a JLink:
# Flash the bootloader with a JLink
$ newt load nrf51_boot
# Show the previously created connection profile for newtmgr
$ newtmgr conn show
Connection profiles:
serial1: type=serial, connstring='/dev/tty.usbserial-DJ004OSX'
# You can see the right tty instance is used below
$ ls /dev/tty.*
/dev/tty.Bluetooth-Incoming-Port /dev/tty.usbserial-DJ004OSX
# Try to run any command using the connection profile above, but
they all freeze and I need to enter CTRL+C to escape
$ newtmgr -c serial1 image list
I know the serial setup is good since I can send commands to the shell
when I flash a firmware image with the same BSP using a JLink, but
newtmgr doesn't seem to do anything meaningful on the nRF51822 for me.
One noteworthy indicator that makes me wonder if serial support is
implemented is that we have LEDs on the HW TX and RX lines and it
doesn't seem the be transmitting any data over UART since the LEDs never
light up. Perhaps newtmgr and serial bootloader support is limited to a
specific MCU family as of 0.9.0-rc3?
Best regards,
Kevin
