Hi team,
if want to meet I2C / SPI / UART / GPIO / 32.768KHz interface, which MCU part with BLE radio do you suggest?
Thansk.
By Small
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi team,
if want to meet I2C / SPI / UART / GPIO / 32.768KHz interface, which MCU part with BLE radio do you suggest?
Thansk.
By Small
Hi,
I am afraid I don't understand your request. Could you please be more specific?
Appreciate your comprehension,
Best regards,
Hi team,
Please see above block diagram.
we need I2C / SWD(debug) / SPI / UART / unused GPIO / 32.768KHz / 48MHz interface.
ex:
I2C IF is pin? and pin?
SWD IF is pin? and pin?
SPI IF is which 4 pin?
UART IF is pin? and pin?
Unused GPIO are pin? and pin?
32K.768KHz is pin? and pin?
48MHz is pin? and pin?
Thanks.
Small
Hi,
Here is the solution you can come to:
I'll let you test the same with SysConfig.
Regards,
Hi,
Thanks to the screenshot you have shared, I now understand the confusion.
First of all, as you can see on the screenshot I have shared, the pins 26 and 27 are left unassigned - so you can use them for the 32 kHz clock input.
I understand you are pursuing a slightly different approach, where you desire to "reserve" the LFXT pins beforehand - I recognize this is a good practice and it may avoid confusions later.
The issue you have is caused by SysConfig not automatically selecting the pins for the LFXT (I am not sure why, I'll report this to the team).
So, when you reserve the LFXT, you see the following:
You should then select manually the signals to use ("P" and "N") and the pins associated:
Two warnings may then appear (they are benign). These are raised because the signals are not routed to a connector on the launchpad. You can remove these clicking on "ignore".
I hope this will help,
Best regards,