there is typically not enough I/O on the WLCSP for full keyboard mapping... which is why we typically use the QFN48. You can check out the reference design files at the URL below..
I don't really need a full keyboard mapping, I just want to be able to send some data via Bluetooth. And this data can be anything it doesn't need to be full keyboard. Can I reduce the I/O's in the code to be able to do that?
It is definitely doable, but you will not be able take advantage of the readily available keyboard reference design. You will, however be able to use the reference code for the full keyboard, modify it, and develop the desirable code for your mini keyboard applications. With that, you can use our CSP chip for the keyboard.
Hi Zeina,
there is typically not enough I/O on the WLCSP for full keyboard mapping... which is why we typically use the QFN48. You can check out the reference design files at the URL below..
http://support.dialog-semiconductor.com/ref-designs
Best regards, JE_Dialog
Hi,
I don't really need a full keyboard mapping, I just want to be able to send some data via Bluetooth. And this data can be anything it doesn't need to be full keyboard. Can I reduce the I/O's in the code to be able to do that?
Thanks
Zeina
It is definitely doable, but you will not be able take advantage of the readily available keyboard reference design. You will, however be able to use the reference code for the full keyboard, modify it, and develop the desirable code for your mini keyboard applications. With that, you can use our CSP chip for the keyboard.