This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2640R2F: problem configuring/programming a 32-bit cc2640r2 module

Part Number: CC2640R2F
Other Parts Discussed in Thread: LAUNCHXL-CC2640R2, UNIFLASH

Dear all,

I’m trying to program a HM-19 module based on a 32-pin cc2640r2f chip.

I wired the module to the related launchpad LAUNCHXL-CC2640R2 through pins TMS, TCK, RESET, VCC, GND. The first time I connected it, the module was locked, so I erased the whole flash, as suggested, to load my customized firmware.

As expected, the result is that the module is unlocked and fully programmable without errors by using both CCS9 and Uniflash.

Once erased, programmed the module via CCS9 by using, in turn, several default projects, such as simple_peripheral, project_zero, and so. Unfortunately, none of them work on the module. Of course, all the tested projects work fine on the launchpad, but they are not working on the module. UART, i2c, BLE beacon are not working, so it is not so easy to me to have a feedback from the board to understand the problem.

I just observed that the cc2640r2 chip on the launchpad is provided with 48 pins, whilst the cc2640r2 chip on the module is provided with 32 pins. Could it be a problem of GPIO enumeration, name, or mapping between the two versions of the chip? In case, is there a pin configuration file (or a basic project) working with the 32-pin version? Conversely, which could be the problem?

Thank you!