Hi Ohad, > > Download TI NFC init script during nfcwilink open operation, > > after the NFC channel is registered with TI shared transport. > > TI NFC init script is written in BTS format. > > First, read the chip version via a special vendor specific command. > > Second, we request the relevant BTS file from the user space, and > > then send the BTS commands to the chip. > > nfcwilink_open() begins by calling the shared transport's > st_register() function, which also seem to be loading, parsing and > sending a BTS firmware to the device. > > Does it mean that two firmwares are needed for these NFC devices ? Yes, TI NFC chip requires 2 different init scripts: 1) General init script for all cores (HCI commands), which comes first 2) NFC init script only for the NFC core (NCI commands), which comes second > From a quick look it seems that much of the boilerplate code for the > BTS handling is quite similar; any way to avoid some of the code > duplication (something the shared transport code doesn't try very hard > to do ;) ? There are several major differences between the two: 1) The vesion read in st_kim is the BT chip version, using the standard HCI_Read_Local_Version_Information command. This version is regarded as the general chip version. The version read in the nfcwilink is a different version using a special vendor specific NCI command. This version is regarded as the NFC chip version. 2) The NFC init script is in NCI commands, while the general init script is in HCI commands. 3) In NFC, we want a simplified BTS init script, e.g. with only ACTION_SEND_COMMAND. No waiting, sleeping or other actions... To summarize, it's a new core with different commands (NCI and not HCI). We chose BTS to make it simple and familiar, but it's a simplified BTS, and we handle the actions differently. Thanks & BR, Ilan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
