[riot-notifications] [RIOT-OS/RIOT] Particle boards: Support monofirmware builds and uploads (#12751)

[chrysn]

@chrysn commented on this pull request.



> +#endif
+#ifdef BOARD_PARTICLE_BORON
+    .platform_id = 13,
+#endif
+#ifdef BOARD_PARTICLE_XENON
+    .platform_id = 14,
+#endif
+
+    .module_index = 3, /* MOD_FUNC_MONO_FIRMWARE from dynalib/inc/module_info.h */
+};
+
+#else
+typedef int dont_be_pedantic;
+#endif
+
+/** @} */

I've picked the parts from the original sources, and as with the firmware addresses it's as weird to use as the module info (unless you're building a firmware that uses all their ecosystem).

What I couldn't figure out though is why this isn't interacting with the baud-rate-600 automatism (which I'm not particularly fond of but haven't contributed anything better either...). I *can* use the command line reset with

```
[ go to bootloader mode using buttons ]
[ it's blinking yellow ]
$ make BOARD=particle-xenon PARTICLE_MONOFIRMWARE=1 -C tests/usbus_cdc_acm_stdio all flash term PORT=/dev/ttyACM0
[...]
> help
Command              Description
---------------------------------------
text                 Generates long text for testing stdio buffer
reboot               Reboot the node
version              Prints current RIOT_VERSION
bootloader           Reboot to bootloader
pm                   interact with layered PM subsystem
ps                   Prints information about running threads.
> bootloader
[ blinks yellow again and accepts uploads ]
```

but just setting baud rate 600 reboots the board without going to the boot loader. Is there any further configuration necessary to enable this?

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/12751#discussion_r518706806
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20201106/129b2766/attachment-0001.htm>