Closed elsalahy closed 4 years ago
Please feel free to comment.
Relevant updates: ST meeting yesterday (19/05/2020):
CC: @johanstokking @wienke @azerimaker
- ST is targeting releasing the WL boards/chips and the SW officially in December 2020.
This is also when we can get access for the first time?
- ST is facing certification issues with the current boards design and predict a change in design.
Is this included in the December timeframe or not?
- ST (Jean-paul) is working on WL SOC LoRaWAN FUOTA production ready SW.
Do you have info? How do they do verification, is there delta support, is it dual bank or does the bootloader overwrite the firmware, is there a manifest?
- Mbed OS integration with the new SOC is still being internally discussed.
We don't need this, do we?
- Benjamin said they might try to convince us to use ST SAFE solution instead of Microchip SE
Doesn't sound very convincing yet. Would be interested in hearing price, power consumption, MoQ and feature set comparison.
- ST is targeting releasing the WL boards/chips and the SW officially in December 2020.
This is also when we can get access for the first time?
I think it only affects that we can't publicly share info,code, applications, design of the SOC.
- We have SW access (internal development hub)
- We have early access to the dev boards.
- Not sure about the purchase situation of volume quantities of the SOC, @azerimaker or @wienke ?
- ST is facing certification issues with the current boards design and predict a change in design.
Is this included in the December timeframe or not?
Yes included.
- ST (Jean-paul) is working on WL SOC LoRaWAN FUOTA production ready SW.
Do you have info? How do they do verification, is there delta support, is it dual bank or does the bootloader overwrite the firmware, is there a manifest?
- Mbed OS integration with the new SOC is still being internally discussed.
We don't need this, do we?
No we don't, If they add official support, it would be interesting which LoRaWAN stack they will use.
- Benjamin said they might try to convince us to use ST SAFE solution instead of Microchip SE
Doesn't sound very convincing yet. Would be interested in hearing price, power consumption, MoQ and feature set comparison.
I'm not convinced as well, but Benjamin focused on the use of MC secure element and mentioned that they might take some action to try to persuade us by reporting this to the ST security solutions department.
Can you answer the question on the FUOTA?
but Benjamin focused on the use of MC secure element and mentioned that they might take some action to try to persuade us by reporting this to the ST security solutions department.
OK let's hear what they come up with
Can you answer the question on the FUOTA?
Yes, sorry escaped it by mistake, Benjamin had little technical info on the topic and asked me to send Jean-paul an email to inquire about further technical details, which I did and I have you in the CC.
but Benjamin focused on the use of MC secure element and mentioned that they might take some action to try to persuade us by reporting this to the ST security solutions department.
OK let's hear what they come up with
Yes
The 9th of December is the release data of the STM32WL HW and FW The HW V0.2 is in production (100 nodes initial patch) Closing the issue due to inactivity, and it can be re-opened in case there is a HW design change
Summary:
In this issue, we will focus on the requirements and HW design discussions and decisions listed here.
This issue will act as an umbrella, linking to other discussion issues of the device subelements such as sensors, power supply design and enclosure design.