I have a MCU which runs at 3.3 V, and have interfaced that with a BC660K-GL through the main UART port. Due to prototyping reasons the VIO_SEL pin was unfortunately not connected to GND as was specified in the design guide (it’s at the bottom of the chip, therefore difficult to solder). Also, the 1 kOhm resistors were left out as well.
Now the problem is that my main MCU is not able to communicate with the BC660K, even though all the other connections are as they should be (as far as I can tell). So the question is, could the reason for the problem be that VIO_SEL is not connected to GND (or the missing resistors)? Or should it be able to function nonetheless?
Any feedback is much appreciated!
N.B. With the BC66 I managed to interface it to a 3.3 MCU with the main UART port, without any level conversion and then went fine (even though the hardware design guide advises to use level conversion). So I was hoping that for the BC660K-GL the same applies.
I think we can check by the following methods
1、First, just test whether main_tx/rx of the module is communicating properly
2、Determines whether the baud rates of the mcu match
We are also facing the same problem. In our prototype BC660K chip set is interfaced with MCU and VIO_SEL signal is floating. BC660K chip is not responding to any AT commands sent through the main UART. No sign of chip set alive.
Is there any way to fix this situation?
How to identify if the chipset is powered up and ready to respond to AT cmds?
Any pointers to resolve this issue will much appreciated.
Thanks.
pls note
1.The BC660K will turn on automatically when powered on, but you need to insert a SIM card or connect a SIM card
2.You can also supply 3.3V to the VBAT pin of the BC660K to try,If the BC660K starts up properly, the VDD_EXT will output 1.8V
Do we need SIM to be inserted for getting response to basic AT command?
Basically we are not getting any response from the BC660K chip for even “AT\r\n” cmd.
What about VIO_SEL signal? If is ok if this is floating or it must be connected to ground to get the chip working?
We are not able to make any progress, need support on resolving this issue.