- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
They are using ST32 MCU . I don't know exact product number
We supplied CYBT-343026-01 sample module.
They want to see bluetooth operate properly when booting, But they failed.
They want to know whether module writing operation is needed.
They already attached the BT module in their own PCB Board.
In my opinion,sample module has own firmware binary already. Is that right?
and I think they should upload kernel driver and call bt stack to bring up bluetooth
Maybe they need to reg on first with GPIO PIN control.
I dont have an experience with ST32. In that case what shoud I check it first?
Please guide to bring up in that situation.
Many Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The sample module could be blank and doesn't come with EZ-Serial firmware installed.
How is the 343026 going to be deployed? Is it going to be used in controller/application mode, or simply as EZ-Serial tunnel?
You can start verifying it by:
- Force to burn the latest EZ-Serial firmware again, via HCI UART.
- Try to detect logs via PUART.
- Try to send commands via PUART, to see if it responds.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
The sample module could be blank and doesn't come with EZ-Serial firmware installed.
How is the 343026 going to be deployed? Is it going to be used in controller/application mode, or simply as EZ-Serial tunnel?
You can start verifying it by:
- Force to burn the latest EZ-Serial firmware again, via HCI UART.
- Try to detect logs via PUART.
- Try to send commands via PUART, to see if it responds.
Best regards
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks. Its very helpful