• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 17 subscribers
  • Views 399 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Problem debugging custom CC2431 board

Frank Chuang
Prodigy 20 points

Other Parts Discussed in Thread: CC2431

We are having trouble debugging a custom cc2431 board using the SmartRF04EB. After connecting the prototype to the P14 SoC debug header the LCD on the SmartRF04EB turns off, which we assumed to mean that it has detected the board. However, the board does not show up on the TI SmartRF Flash Programmer device list. If the problem is with our board, what are the things we should check to fix the problem? Thanks!

  • 0
    Mastermind 8170 points

    Without a CCxxxx plugged into or connected in anyway to the RF04 board the RF04 board should show up in device manager as follows when connect via USB and turned on: (see attached photo):

    --Cebal controlled devices
    ---- Chipcon SRF04EB  

    If this is OK  then there are two things to consider.  If your custom cc2431 board  is correctly designed it has a pull up resistor and cap on the /reset line. This is a problem for the RF04. The voltage from your pull-up prevents the bi-directional level translator (ST237) on the RF04 from changing to an output. Also many people miss the need to provide power from the custom cc2431 board  to the RF04 via pin 2 on the P14 SoC debug header to power the custom board side of the level translator.

    Let us know how you make out...

  • 0 in reply to H Stewart
    Prodigy 20 points

    Thanks for the reply! The RF04 board seems to be functioning properly and can program the EM's without any trouble. Regarding the pull-up resistor, it doesn't seem like we have any on the reset line. Our board designer referenced the schematic of the EM to design the board. However, P2.1 is connected to a separate component (an accelerometer) on the board. Could this be interfering with the debugging? Thanks again for your help!