CC3000-Pmod

Is there a reference design or example to get a CC3000-Pmod wi-fi adapter working on the Zedboard? This adapter is made to be used with the Xilinx Spartan-6 FPGA LX9 MicroBoard.

0 bhfletcher over 13 years ago

It is on our schedule, but we have not started the work yet. The design for the LX9 MicroBoard is in the process of being updated to 14.4, and then the ZedBoard work will be next. Please stay tuned!
Bryan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bhfletcher over 12 years ago

Although we don't have the CC3000 working with ZedBoard yet, I have had reports that off-the-shelf USB wireless dongles work with ZedBoard and Linux. This has the added advantage that the Linux driver is already written.
Bryan
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago

Have you had any luck with the CC3000-Pmod adapter and the ZedBoard? I'm currently trying to make it work, but I'm having problem with the initialization of the CC3000.

Regards,
Darius
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 12 years ago

I also have a dark cold CC3000 Pmod sitting next to my zedboard right now, and am trying to find time to interface it by converting the LX9 files.

So I'm also extremely interested in this conversion, since I want to integrate the TIWI-SL WiFi chip into my product.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Former Member over 11 years ago

Hi all,
we are using the PMOD CC3000(TIWI) with an SP601 board under ISE/EDK 14.7. We have made the effort to port the ref design of the microboard LX9 to the SP601 board. The issue was onto the GPIO IRQ port mapping with the interrupt controller.
Now we have the example of the web server page from the LX9 that is working with the SP601 board under 14.7 version.
Actually, we are trying to use the pmod wifi module onto the zedboard using the XSPI_PS IP. It seems that we are closed to have it working but some delay mechanism seems to be the issue.
Inside the code, there are multiple call to the function _delay_cycles but it is a simple for loop which wait a certain amount of time... And comments in the code do not help to understand the real timing pause that is exepected. According to the microblaze design that is working at 100 MHz and the ZYNQ at 666MHz the rules would be to wait 6 times more, but unfortunately, it is not working...
Does some body have any detailed documentation onto the state machine of the CC3000(API) and the timing constraints associated?
Regards,
Julien
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 peterfenn over 11 years ago in reply to Former Member

According to notes from TI in context of original MSP430 design:
__delay_cycles(6000000) is about 0.24 seconds
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel