npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

wifi-cc3100

v0.0.2

Published

Node.js module for connecting CC3100 to the Tessel.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

linusulinusu

Keywords

Readme

wifi-cc3100

Node.js module for connecting CC3100 to the Tessel.

I have started to look at getting the CC3100 to work with the tessel. This is the next version of the wlan chip currently used in the tessel. Improvements over the current chip would be 802.11n support, more concurrent sockets, higher throughput and less buggy.

Hardware

Connecting the CC3100 to the tessel is easiest done with the CC3100BOOST, which is a small breakout board for the actual chip. Hooking it up to the tessel is as easy as connecting 7 cables. You can use any port on the tessel for this, since they all share the same SPI channel.

Visualization

| Name | Tessel | CC3100BOOST | Description | |------|--------|-------------|-------------------------| | GND | 1 | 3.2 | Ground | | | | | | | SCK | 5 | 1.7 | SPI Clock | | MISO | 6 | 2.7 | SPI master in/slave out | | MOSI | 7 | 2.6 | SPI master out/slave in | | CS | 8 | 2.3 | SPI Chip Select | | IRQ | 9 | 2.2 | Interrupt request | | nHIB | 10 | 1.5 | Hibernate | | | | | |

Software

The source code for the software is available in a GitHub repo at https://github.com/LinusU/wifi-cc3100. Easiest to get started is to clone the repo and run the test-file included. It has the port hard-coded to B so either use that or edit test.js.

git clone http://github.com/LinusU/wifi-cc3100.git
cd wifi-cc3100
tessel run test.js

It will print out a lot of debugging info and hopefully also print out Ready! which indicates that the board was reseted and initialised. The test code will right now try to connect to a unsecured network called FlatRoof, just because that is my setup.

Hacking

To get started with development of the module just start by editing test.js to include what you want to test. Then edit index.js to add the implementation. The implementation of the messages is inside lib/msg.js, it implements serialising and deserialising to the wire. The protocol is implemented in lib/protocol.js and can be used to send a message to the chip, and then wait for response.

index.js has top level methods that packs together a message and sends it via the protocol. The main method here is protocol.send(opcode, descriptors, payload, cb). opcode, descriptors and payload are described on the TI Wiki, see Protocol description below. cb is a callback that will be called once the chip answers.

I recommend downloading the SDK to see exactly what descriptors and payload should contain. The name of the function corresponds to the messages, search their driver source code.

Links