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.

CC2530 EM Wrongly Detected as CC2500 & CC2550 Why ?

Other Parts Discussed in Thread: CC2530, CC2500, CC2530EM, ALLIGATOR

Following the CC Debugger connection in the Usermanual i have connected the CC debugger with following configuration with some minute changes

But the problem is the CC debugger LED becomes green after multiple press(trails) of Reset (when connected to SOC in my case i am connecting it to EM board of CC2530

More importantly after the CC debugger gets detected by showing a Green LED status,its been detected as CC2500 Transceiver instead of CC2530 why so ???

  • Pin 2 has to be connected to DUT vdd. This pin senses the voltage level for the build-in level shifters.

  • TER said:

    Pin 2 has to be connected to DUT vdd. This pin senses the voltage level for the build-in level shifters.

    No Change in the Behaviour
  • Could you post a picture that clearly show how you have connected the debugger to your board and also screenshots of SmartRF Studio showing the issue.

  • TER said:

    Could you post a picture that clearly show how you have connected the debugger to your board and also screenshots of SmartRF Studio showing the issue.

    Schematic updated please find it above
    below are the schematics when its not detected showing red status

    after pressing reset abruptly 10 to 15 times i have got the device identified
    are there any debug methods to verify whether my CC debugger is ok or faulty one of my friend has given it me saying it has been a year he used it
  • Could you post a picture that clearly show how you have connected the debugger to your board. A drawing from the UserGuide does not tell me anything.

  • TER said:

    Could you post a picture that clearly show how you have connected the debugger to your board. A drawing from the UserGuide does not tell me anything.

    Here is the schematic same suggested by user manuals 
  • Hi, 

    Do you have another CC debugger to check your device with?

    Additionally, is there any particular reason you have connected the SPI lines?

    Finally, are you sure that "Vdd (from target)" pin getting the same voltage level as the cc2530?

  • I assume this is a very simplified schematic and that does not tell me anything. The reason I ask about a picture is to see if you have actually done as shown in the schematic. And as also Igor pointed out, how have you connected power and other pins that looks NC? Is this a board you have developed?

  • My schematic is simply

    Debugger    CC2530EM

        GND                GND

        VDD                VDD

        VSense           VDD

        DC                     DC

        DD                     DD

        RST                  RST -- through RC filter 2.7K and 1nF 

    Have Left the SPI connections unsoldered for now,earlier it atleast use to show a wrong chip now even its also not shown 

    i don't  have another CC debugger but i have a Smart RF board using which i have updated the firmware of CC debugger also (by this can i confirm my cc debugger is fully functional ?? )

  • Well, if you aren't willing to share a picture with us, at least, please provide us with measured voltage levels on VDD and Vsense pins, plus oscilloscope readings of RST DC and DD signals

  • Igor Sherer said:

    Well, if you aren't willing to share a picture with us, at least, please provide us with measured voltage levels on VDD and Vsense pins, plus oscilloscope readings of RST DC and DD signals

    Voltages
    VDD       3.23V
    Vsense 3.23V
    DD         Not changing alwayz at 3.2V
    DC         Not changing alwayz at 3.2V
    RST       always at 3.2V no change even if reset button on CC debugger is pressed
  • Are the DD, DC and RST voltages were measured with DVM or an oscilloscope?

  • If you don't get a reset when pushing the button I would disconnect the reset line and measure on the debugger again. If you don't get a reset when this line is NC I would recommend getting a new one.

  • Igor Sherer said:

    Are the DD, DC and RST voltages were measured with DVM or an oscilloscope?

    yeah using a DVM
  • TER said:

    If you don't get a reset when pushing the button I would disconnect the reset line and measure on the debugger again. If you don't get a reset when this line is NC I would recommend getting a new one.

    i have tried to remove entire setup and just tried to see the rst state on scope from the box connector still  it doesn't generated any sort of signals,but how come it has upgraded its firmware ???
  • Try to reflash the CC debugger FW with smartRF05EB. The FW can be found in the following path:

    ...\Texas Instruments\SmartRF Tools\Firmware\CC Debugger\cebal_fw_srf05dbg.hex

  • Igor Sherer said:

    Try to reflash the CC debugger FW with smartRF05EB. The FW can be found in the following path:

    ...\Texas Instruments\SmartRF Tools\Firmware\CC Debugger\cebal_fw_srf05dbg.hex

    i have already said in the above posts that , i confirmed CC debugger is functioning proper when i tried to update the firmware using smart RF board no 'old' tag is shown now any how i have reflashed it again with your suggestion
  • And what is the result???

    In any case, to be able to help you with your problem we need some more info. A picture worth a 1000 words

  • Igor Sherer said:

    And what is the result???

    In any case, to be able to help you with your problem we need some more info. A picture worth a 1000 words

    No change same is the state
    previously there was a short in the board,now it is removed the voltage readings at the pin
    Measured using DSO - DC coupling
    Readings at the Box connector of CCdebugger
    VDD 3.3V
    Vsense DD DC GND  RST and other pins 0V
    Readings after connecting EM board to the CC debugger
    VDD 3.3V
    Vsense 3.3V
    DD DC GND RST and other 0V
    SPI interface not connected 
    pressing reset switch did not make any change to the reset PIN state, even at the cc debugger box connector or even after the RC filter output going to EM Reset Pin,is reset pin is supposed to change its state for at least a few ms after the button press ??
    what pictures you exactly want ? i have clearly explained them in previous replies  how CC debugger is wrongly detecting cc2530 SOC as cc2500 (with pictures ) after many switch presses, now it shows no chip
    first of all i want to confirm whether CC debugger is functioning or not ?
    i have made an attempt to update the firmware ,it has succeeded  and i confirmed it is functioning proper are there any other approaches to make sure its is functioning proper 
  • If you take the debugger, plug the USB cable in and short pin 2 and 9. If you monitor the reset pin it should change state when you press the reset button. Mine did anyway.

  • TER said:

    If you take the debugger, plug the USB cable in and short pin 2 and 9. If you monitor the reset pin it should change state when you press the reset button. Mine did anyway.

    Thanks for your  continuing support i have now shorted the VDD and VSense still then the problem is not resolved

    now RST VDD Vsense are High at 3.3V
    when itried to view the RST pin 
    RST pin out of CC debugger
     
    RST pin state out of RC filter with 2.7K and 1nF as shown in user manual
    i believe RST pin must be held low at least 1uSec, by above diagrams we can see it was low for greater than 5msec,the pulses on RST pin are they due to switch debouncing ??? 
     
    is this RST state appreciable,some how i tried even to short my rst pin with ground for a momment even that also did not help 
     
    and on DS and DD i have seen a pulse going low for 20msec exactly,by default they are pulled up
  • Hello DARAM,

    You could have some grounding issues.  Use an alligator clip and connect to the GND (Right most Upper Terminal) and the EM connector to see if that helps.

    Did you happen to drop the EM by any chance?

    Thanks,

  • greenja said:

    You could have some grounding issues.  Use an alligator clip and connect to the GND (Right most Upper Terminal) and the EM connector to see if that helps.

    Did you happen to drop the EM by any chance?

    i did not understand that, can you please explain in detail. i have tried to view the wave forms b/w EM GND and the RST pin of EM only and the EM is very new and its fully working with a smart RF board 

  • Hello DARAM,

    Anytime I have encountered that problem it has either been because of poor grounding or if I dropped it.  If you don't have this problem when flashing through the SmartRF, then the problem would have to be with the cable connection to the EM.  The cable connection problem is more likely a result of a poor ground.

    Thanks,

  • i Solved my problem like this

    Turned a SmartRF board to CC debugger and tired to see the clock and data sequenced which showed the actual sequences and verified it over the custom board

    the problem is with poor grounding,which was identified and rectified

    then its connected to CC debugger which solved the problem

    Thank you each and every one for your continued support