CC3000EM - CC3000 Evaluation Module and BOOSTXL-SENSHUB Sensor Hub BoosterPack Problems

Randal Riedinger

Other Parts Discussed in Thread: CC2533

I'm having problems with both a EK-LM4F120XL and EK-TMC123GXL LaunchPads with a BOOSTXL-SENSHUB Sensor Hub BoosterPack and CC3000EM - CC3000 Evaluation Module. Are these a supported configurations? The BOOSTXL-SENSHUB Sensor Hub applications seem to work OK except for the airmouse. I'm trying to get the Basic Wifi Application working with the CC3000EM and I was getting spurious interrupts from the WL_SPI_IRQ/RF_GPIO1 line . I'd like to have a copy of the Sensor Hub BoosterPack PCB layout and can't find it. It looks like the RF_GPIO1 (PE2) and RF_GPIO2 (PE3) are getting shorted out to something else on the BOOSTXL-SENSHUB board even without the CC3000EM present. I don't see anything on the schematic that should be affecting this. I'm using a modified version of the blinky example to pulse the PE2 output as a test. Without the BOOSTXL-SENSHUB installed the PE2 output (Image #1) and PE3 input (Image #2) look normal and are shown below. With the BOOSTXL-SENSHUB installed they both PE2 and PE3 look like the third (Image #3).

Image #1 PE2 output EK-LM4F120XL only.

Image #2 PE3 input EK-LM4F120XL only.

Image #3 PE3 output EK-LM4F120XL with BOOSTXL-SENSHUB installed, PE3 input is identical.

over 12 years ago

0 Randal Riedinger over 12 years ago

Prodigy 140 points

Should say "Image #3 PE2 output EK-LM4F120XL with BOOSTXL-SENSHUB installed, PE3 input is identical."

0 Stellaris Dexter over 12 years ago in reply to Randal Riedinger

TI__Genius 17225 points

What is the configuration mode of the GPIO on the CC3000? Most of the EM modules have these GPIO and not all the GPIO are configured as input by default. I agree it looks like there is a contention on the line. Perhaps the CC3000 and the LM4F120 are both trying to drive the pin?

0045.Sensor_Hub_Booster_Pack Rev A Test.pdf

I've attached a PDF of the board layout enlarged. The original is in Mentor PADS. It should be fairly easy to trace out the PE2 and PE3 lines they appear to only have one via each and go nearly vertical on the bottom and then approximately horizontal on top to the EM connector. The board rules were set for 6 mil trace and space. If you need to hopefully this will help you trace the lines and find a possible short.

I suggest verify the CC3000 configuration for those GPIO first.

Dexter

0 Stellaris Dexter over 12 years ago in reply to Randal Riedinger

TI__Genius 17225 points

Randall,

I also added a GPIO output on PE2 and PE3 from the Stellaris. I then looked at this on the oscope with and without a sensor hub attached. the signals were identical and full range 0 to 3.3v on my launchpad + sensorhub.

Also to answer you initial question, the CC3000 should work on the sensorhub but so far the only "officially" supported interface is the CC2533 used in the air mouse demo.

Dexter

0 Randal Riedinger over 12 years ago in reply to Stellaris Dexter

Prodigy 140 points

Thanks, but I have the shorting problem with the CC3000 removed. I am wondering if my Sensor Hub is bad or if it is a generic problem. I don't want to have to waste time returning the one I have if the replacement has the same problem.

0 Stellaris Dexter over 12 years ago in reply to Randal Riedinger

TI__Genius 17225 points

The sensor hub i have does not show this behavior.

If you can show that there is in fact a short on your sensor hub then i suggest an RMA.

Dexter

0 PAk over 12 years ago in reply to Randal Riedinger

Mastermind 7015 points

Randal Riedinger said:

Thanks, but I have the shorting problem with the CC3000 removed. I am wondering if my Sensor Hub is bad or if it is a generic problem. I don't want to have to waste time returning the one I have if the replacement has the same problem.

I am seeing different behaviours in my sensors:

http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/t/285768.aspx

Arm-based microcontrollers

Arm-based microcontrollers forum

CC3000EM - CC3000 Evaluation Module and BOOSTXL-SENSHUB Sensor Hub BoosterPack Problems