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.

Need Help! Problem when using CC2541 with TPS62730

Other Parts Discussed in Thread: CC2541, TPS62730

Dear TI Engineer,

       I have a problem when using CC2541 with TPS62730.

       I use the P1_5 to control TPS62730. The input of TPS62730 is a stable 3.3V power supply.

       My program read/write the internl Flash of CC2541.

1、I keep P1_5 to low in the whole program, the TPS62730 output 3.3V. The function all goes allright: Connection allright, Read/Write charicteristics allright, Flash Read/Write allright.

2、I keep P1_5 to high in the whole program, the TPS62730 output 2.1V. I use oscilloscope to monitor the output, the 2.1V is stable.

      And Connection is allright, Read/Write charicteristics is allright. But when data is write into Flash and readback, the readback data is all 0xFF.

      Q1:Can't the internal Flash work allright under 2.1V?

3、I set P1_5 to high first, and then set "HCI_EXT_MapPmIoPortCmd( HCI_EXT_PM_IO_PORT_P1, HCI_EXT_PM_IO_PORT_PIN5 );" in initilization.

     Let OSAL to control P1_5.(I'm sure there is no other place using P1_5)

     I use oscilloscope to monitor the output, the waveform is 2.1V when Active and 3.3V when in PM2 mode, as expected. So I think the OSAL control P1_5 allright.

    The device can be seen in LightBlue. But when I try to connect it, the connection cannot be set up. But as described in 1 and 2, when using 2.1V or 3.3V stable output, the connection always can be set up and the Characterstics Read/Write are allright.

    Q2: What's the possible cause of this problem?(Flash Read/Write program is removed here)

    Wishing for your help and advice.

    Yours sincerely,

Frank

  • Hello,

    Are you able to debug with the CC debugger during flash programming?
    For the connection issue, do you have a BLE air sniff log?

    Best wishes
  • Hi JXS,

                Thank you very much for your reply.

                For Q1, I run it in CC debugger, during flash programming,but I can't find why the NV_Read result is 0xFF when powered with 2.1V, while NV_Read result is allright when powered with 3.3V.

                For Q2, I use the packet sniffer and get the log as follows:

    unconnected_HCI_EXT_MapPmIoPortCmd_v1.psd

    unconnected_HCI_EXT_MapPmIoPortCmd_v2.psd

    unconnected_HCI_EXT_MapPmIoPortCmd_v3.psd

  • And I tried the SimpleBLEPeripheral example program in TI BLE1.4.0 stack. I change the P0_7 to P1_5 because I use P1_5 in my board.

  • And I tried the SimpleBLEPeripheral example program in TI BLE1.4.0 stack. I change the P0_7 to P1_5 because I use P1_5 in my board.

    1. With POWER_SAVING disable and HCI_EXT_MapPmIoPortCmd( HCI_EXT_PM_IO_PORT_P1, HCI_EXT_PM_IO_PORT_PIN5 ); enable

        The VCC is keeping 2.1V. The device can be connected and access normally.

    2. With POWER_SAVING enable and HCI_EXT_MapPmIoPortCmd( HCI_EXT_PM_IO_PORT_P1, HCI_EXT_PM_IO_PORT_PIN5 ); disable

        The VCC is keeping 3.3V. The device can be connected and access normally.

    3. With POWER_SAVING and HCI_EXT_MapPmIoPortCmd( HCI_EXT_PM_IO_PORT_P1, HCI_EXT_PM_IO_PORT_PIN5 ); both enable

        The lightblue shows "The periperal disconnected while being interrogated" when try to connect.

        The waveform of VCC in 3 is shown in the following photo, which I think is allright.

        I think it's not a hardware problem, because of the results in 1 and 2. And now I'm using the SimpleBLEPeripheral example program, there should be no problem in software.

        I'm confused in this problem. Is there anybody who has succeeded with POWER_SAVING and HCI_EXT_MapPmIoPortCmd( HCI_EXT_PM_IO_PORT_P1, HCI_EXT_PM_IO_PORT_PIN5 ); both enable?

        Please help!

    Frank