Hello Sebastian,
Thank you so much for your reply.
1. I was hoping to have it setup so that we could use our Rohde & Schwarz CBT tester to test it.
Just like what we do with our other BLE chip running Direct Test Mode
(2wire connection, 9600, no flow-control, connected to the CBT BLE tester only,
and the PC is controlling the CBT via R&S CBTgo Software).
2. On the project folder of the QN902x SDKv1.4, I flashed the \prj_proxr (proximity application,
Keil MDK lite compiled).
I was hoping the described CFG_TEST_CTRL_PIN (which I enabled) in user_config.h
once defined will automatically enable the DIRECT TEST MODE whenever the assigned
pin (GPIO_P31 in this case) is connected to ground before powering the board.
3. I tested the proximity application and it worked fine. After which, I shorted the GPIO_P31 to ground.
so that powering-on the board will prepare it in test mode.
4. On the devkit, we removed the R36 and R35 resistors to have the BLE UART0 directly connected
to the MAX3232 board we made (using pins for TXD,RXD,CTS,RTS) since the CBT we use
only supports DB-9 connection. We ensure that the connections are correct prior to running the
BLE Tester application (CBTgo : HCI, 9600, hardware flow-control)
5. But, it seems the CBT is not receiving any response from the QN9020 devkit.
6. I was searching the web for documentations regarding this, and found the
QBlue Production Tool document.
It describes the procedure (in chinese) on how to test the QN9020
with the BLE TESTER (I'm not really sure what BLE test equipment is used).
7. On the NXP website it is the NXP BLE Production Tool (but it supports QN9080 only).
Will try your suggestion. But, we are hoping to get the production tool software I mentioned above
for QN9020 from NXP since our project's deadline for the testing phase is almost over.
Will post again any inquiries/issues we will encounter regarding this matter.
Again, thank you very much!
Best regards,
William
