Looking for UART guidance for the STM32WB05KN Network Co-Processor

[Richard Lowe]

Building a product that utilizes BLE communication and since this is a new product, the STM32WB05KN was chosen due to the BlueNRG line being phased out.

Unlike the BlueNRG line, they have a UART interface that would be advantageous to use, but seems to lack documentation. 
Doesn't seem to be found in the Wiki: WB0 Series Wiki

Can't find it in the um3355 documentation.

Looking for basics, like UART parameters (baud, bits, etc), examples, and maybe some guidance on using DMA and Interrupts.  What pins are required?  Reset, IRQ.......

[STTwo-32]

Hello @Richard Lowe 

You can find some examples on LPUART/UART for the NUCLEO-WB05KZ. You can also find others on the STM32CUBEWB0. for more details about configuration and pinout. You can always check the RM0529 and the datasheet DS14591.

Best Regards 

STTwo-32 

[Richard Lowe]

The board I am currently working with is the X-Nucleo-WB05KN1 : X-Nucleo Board 

That tool does not have a St-Link onboard and is purposed as a Co-Processor.  That is where the documentation is lite and missing some information. 

If being used as a co-processor, what is the compatible baud rate that the host should be configured with?

The documentation is missing for how to update the binary, if needed.  It looks like it is BLE only, which is fine, but what binary is loaded by default?

What pins are required to be used as a co-processor.  From the examples in the X-Cube-WB05N v1.0 release, it appears to only require the RSTN pin aside from the UART pins, but there is also a IRQ line that is used for boot.  Does it require that pin if only using UART communications?

In the X-Cube-WB05N V1.0 package, examples are confusing because the baud rate changes from an initial 115200kps to 912500kps in the application layer.  Which is it?

in the hci_tl_interface.c file it uses none interrupt based communication, but in the app_stm32wb05n.c file it uses interrupt based queries.  Which one is it?  I would assume the htl stack would use the hci_tl_interface that must be implemented, would be the default, but then why is there another method in the application layer?

[STTwo-32]

Hello @Richard Lowe 

This is a new question, could you please select a best answer to this post and answer this question on a new thread. 

Best Regards.

STTwo-32

[STTwo-32]

Hello @Richard Lowe 

First, I'm sorry to be back later to you with an answer. Thank you @Andrew Neil for the continues support. I'm not going add a lot give a getting start guide that may help you. You can find it attached in this post. 

Best Regards.

STTwo-32

[EzraKrause]

Hi @STTwo-32 

Has ST updated the supporting documents on this product yet?

The Getting Started PDF is of no help when using the device as a co-processor via UART.

Regards

Ezra

[Richard Lowe]

I personally, haven't seen any updates to the Getting Started.  After putting too much time into it, we've put the project on hold.  I sure I could spent several hours extracting the parameters and functions from the example application, but don't really have the time to do that.  STM really needs to clarify how to use the STM32W05KN as a co-processor via UART.  I think they dropped the ball on this one.

[EzraKrause]

Hi @Richard Lowe 

Were you able to make some progress with the STM32W05KN co-processor?

I find myself in the same position as you.

Regards

Ezra