1 of 1 people found this helpful
Quite a few questions here, so let me see if I can answer them all.
Datasheet for the 20737S should be available on the website within the next few weeks. Note that since the HW is identical to the 20736/32S, you could use those datasheets (available) in the meantime.
We include support for an NFC tag waking up the BCM20737 over GPIO when a reader reads from the tag. It then sends pre-programmed information over a BLE link which is similar to what’s stored in the NFC tag. An NFC Tag and Reader still required within the application.
The BCM20732/36 and 20737 are indeed source code compatible. However, firmware generated for the 20732 based product cannot be used on the 20736/37 based products and vice versa.
There is just under 30K of free RAM available on the 20736/37 based product. On the 20732 based product, this figure is closer to 20K. More memory is free in the newer firmware based on better patch management in the latest rev. With regards to new features taking space, this is not necessarily the case as many features only occupy RAM once used. For instance, the extra RAM needed for RSA on the 20737 can is only allocated by apps that require the RSA library.
I'm not not sure what's being asked wrt to striping used memory in firmware.
May I ask more about NFC pairing support. Since BCM20737 needs only one GPIO from NFC tag circuit to wake up from sleep, I don't know why this is limited to BCM20737 only. I suppose this is working for BCM20736, or even BCM20732. Am I right?
The NFC feature is only available/supported on the BCM20737[S]
Here's some additional information that may help clarify the previous response:
-NFC is not recommended nor has it been tested on any chip other than 20737
-Our passive tags have been tested with the 20737 only
-the 20737 has security features which can be used in conjunction with the tag for combined use cases.
-Any future development of NFC (or related use cases) is slated for 20737 only.
any app notes on NFC with mentioned chip?
Unfortunately, I am not aware of an AppNote available today which explains how to use the NFC integration capability for the BCM20737S.
Note that with regards to NFC, we only support for an NFC tag waking up the BCM20737 over GPIO when an external NFC reader reads from a separate NFC tag that's included in the same design with our BCM20737S.
Once awaken by the GPIO, the BCM20737S then sends pre-programmed information (placed on the part in the customer's production process) over a BLE link which is similar to what is stored in the NFC tag.
You still need an NFC Tag and Reader within the application. In addition, this feature cannot be used for OOB pairing.
Is this the functionality you are looking for within your application?
I looked at the WICED SDK and cant see any specific code for reading of the NFC tag .
Is there any specific code ?
Also, is there an example schematic or Tag that you have used in testing ?
There are no sample applications available today which shows this functionality in action.