Other Parts Discussed in Thread: CC2640R2F, HDC2010, BQ25120
Good morning, in our BLE product, schematic attached, we are using cc2640r2f surrounded by several sensors, similarly to your sensortag evb.
See schematic attached.
We had in the past for the same product a helpful support by Brandon Fisher, about the HDC2010.
We have on board a micro usb connector, that we use only for charging the battery, through the TI BQ25120 charger.
No USB functionality is in the product.
We would like to change the usb connector, replacing the current with a usb-c type.
Since we need only the charging functionality and the usb-c type has several pins, we woul like to use some other pins for other signals, for instance i2c and jtag.
We would like to export via the usb-c connector the i2c and jtag pins of our meteotracker board.
In this way, while our device would be rechargeable from any usb peripheral, charger, pc etc with a popular cable, we may use the same cable, connected to some proprietary electronic boards, for flashing or to connect other proprietary electronic i2c sensor expansion boards equipped with i2c interface.
The problem would be: since in this way several usb-c signals would be connected to our meteotracker board, what happens when the meteotracker is attached for charging to a usb 3.1 full featured port?
Possibly some conflicts may arise in the usb 3.1 full featured host port.
Stated in another way, we would like to use the usb-c connector only for usb-charging and reuse as most as possible pins for general purpose, avoiding conflicts when a full featured cable is connected to a full featured usb 3.1 host port.
Do you think would be possible, for instance working on cc1 and cc2 pins connections?
In general, do you think would be a risky solution?
Thanks a lot.
Timoteo
