NEW JIRA items within last 24 hours: 1 [ZEP-750] Arduino should support one configuration using original bootloader https://jira.zephyrproject.org/browse/ZEP-750 UPDATED JIRA items within last

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4419 : quark_se_devboard: enable UART0 on the sensor subsystem - https://gerrit.zephyrproject.org/r/4422 : boards: rename Quark SE

Thanks. I can see stm32 is OK in this regard, none of the others appear to be. I'll use interrupt disabling for my code to make it safe until SMP arrives. -- Tixy

Hi Maureen/Iván, I managed to get it working now and my led is flashing :) Thanks!

Hi Euan,

NEW JIRA items within last 24 hours: 1 [ZEP-749] TinyCrypt uses an old, unoptimized version of micro-ecc https://jira.zephyrproject.org/browse/ZEP-749 UPDATED JIRA items within last 24 hours:

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4395 : doc: Add link to 1.5 tagged documentation on /doc homepage - https://gerrit.zephyrproject.org/r/4393 : Merge remote-tracking

Hello Rohit, Rohit Grover <Rohit.Grover(a)arm.com> wrote: I'm glad to know you care about this usecase too, and thanks for sharing this on list, I hope this will be useful feedback for Z's network

If the HAL is only a bunch of headers, then you don't need to build anything. But if you look at the QMSI one, you'll see it's building a lot of stuff, so it may serve as an example.

Hi, Zephyr 1.5.0 was tagged and the merge window for 1.6.0 is now open. 1.6.0 will be released end of November which means the merge window will be open until early November. Release notes for 1.5.0

So the best way forward is to add the device headers to /hal/asf and change sam3 to the family/series hierarchy? There are some really weird things going on with the Atmel drivers, especially some

NEW JIRA items within last 24 hours: 0 UPDATED JIRA items within last 24 hours: 2 [ZEP-635] Add FS API to grow a file https://jira.zephyrproject.org/browse/ZEP-635 [ZEP-622] Add FS API to

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4382 : Bluetooth: Clean up feature test macros UPDATED within last 24 hours: - https://gerrit.zephyrproject.org/r/4378 : Bluetooth:

NEW JIRA items within last 24 hours: 5 [ZEP-744] USB WebUSB https://jira.zephyrproject.org/browse/ZEP-744 [ZEP-748] Enable mbedtls_sslclient sample to run on quark se board

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4378 : Bluetooth: Extend HCI to cover all BLE commands and events - https://gerrit.zephyrproject.org/r/4365 : test_ctr: fix

NEW JIRA items within last 24 hours: 1 [ZEP-741] Network TCP API is adhoc and makes arbitrary assumptions https://jira.zephyrproject.org/browse/ZEP-741 UPDATED JIRA items within last 24 hours:

Not entirely. A particular SoC may provide means of setting/resetting GPIO in an atomic fashion. Driver implementation should use such mechanism if present. For instance, STM32 GPIO peripheral has 2

NEW within last 24 hours: - https://gerrit.zephyrproject.org/r/4341 : Bluetooth: HFP HF: Initialize Handsfree profile - https://gerrit.zephyrproject.org/r/4359 : ksdk: Allow KSDK selection via

I figured that interrupt locking was the way to go, was just wary of it since it would break with SMP. Guess when that arrives all interrupt disabling will need to be audited and converted to