Thorvard

Its software, i've analysed the out of the box demo shortly after release of the LP.

Hi Rei, while developing an application i took a look at the schematics of the CC3200 LP and noticed that many Pins are not connected to the booster pins and therefore not usable without modifying the Launchpad, or are already in use by system components: P1.3 -> Switch3, Accelerometer INT (detachable from sensors by jumper) P1.9 -> Yellow LED, SCL (detachable from sensors by jumper) P1.10 -> Green LED, SDA (detachable from sensors by jumper) P3.3 -> FTDI_TX P3.5 + P3.6 are not connected by default P3.9 -> Red LED P4.1 - P4.8 are not connected by default P4.9 -> JTAG_

Sidenote: when you want to paste text without formatting like font, size, etc., just press ctrl-shift-V

This thread could be a good start: http://forum.43oh.com/topic/1312-nokia-5110-display/

The cc3000 does not correctly implement mDNS out of the box. The correct implementation of mDNS works like this: - you type for example http://target.local in your browser - the mDNS service on your machine multicasts a query paket to the network asking which machine is named "target.local" - the target listens for mDNS queries on upd port 5353 - the target receives the query paket, checks the name and when the name in the query matches its own name it sends a reply paket publishing its IP (mDNS advertising paket) - the paket is received by your machine and resolves "target.local" to

The wireshark capture looks fine to me, the cc3000 is multicasting the mDNS pakets correctly (as far as the cc3000 is correct). But one question: do you have a mDNS client installed on your pc? Windows normally doesnt have a mDNS client, without it target.local will always fail. You can either install iTunes (which includes a mDNS service called Bonjour) or only the Bonjour service, Apple offers a standalone Bonjour version for airprint. Bonjour standalone: http://support.apple.com/kb/DL999 iTunes: http://www.apple.com/itunes/download/

The Page reports 404 Not Found, wrong url?

Can you post a Wireshark screenshot of the mDNS packet, i like to see if its a broadcast or a multicast packet. I've posted an updated fw_patch.h in the 43oh forum: http://forum.43oh.com/topic/5216-updated-fw-patchh-for-cc3000-firmware-126/ I've tested it on the Tiva-C Launchpad, but it should work on the 5529 launchpad too. Very old firmwares of the cc3000 had problems with multicast pakets. The slow loading of config.html is normal since the webserver send for each client.print() a seperate paket. A normal tcp paket can be about 1500 bytes large, but beware, in cc3000_common.h t

I replied to your post over at stelarisiti in the mDNS library thread. Another problem might be that your Router isnt forwarding multicast pakets between LAN and WiFi, my former router had that bug, is was an Easybox803 router, now with my new Fritzbox everything is fine. I don't know if the mDNSAvertiser bug returning bogus values is fixed in the last firmware, just ignore the returncode, i think the only moment it fails might be when all of the 4 ports the cc300 supports are in use or when it isnt connected to an access point. best regards, Thorvard

The Example i included is for the Tiva-C Launchpad which uses different pins for the boosterpack than the LP5529, you have to change at line 51: // Set communication pins for CC3000 WiFi.setCSpin(PE_0); // 18: P2_2 @ F5529, PE_0 @ LM4F/TM4C WiFi.setENpin(PB_5); // 2: P6_5 @ F5529, PB_5 @ LM4F/TM4C WiFi.setIRQpin(PB_2); // 19: P2_0 @ F5529, PB_2 @ LM4F/TM4C to: // Set communication pins for CC3000 WiFi.setCSpin(P2_2); // 18: P2_2 @ F5529, PE_0 @ LM4F/TM4C WiFi.setENpin(P6_5); // 2: P6_5 @ F5529, PB_5 @ LM4F/TM4C WiFi.setIRQpin(P2_0); // 19: P2_0 @ F5529, PB_2 @ LM4F

Good news everyone, its working again After running the 'getting_started_with_ap' example from the cc3200 SDK i was able to put the device into smartconfig mode and connected it to my router, i had to use the iOS App because the Java Webbrowser code that Ti supplied wasnt working. But the problem with flashing still existed, so after wasting another few hours i came to the conclusion to format the flash using the Uniflash Tool, despite the fact that the Uniflash manual does not recommend it. But hey, the Launchpad wasnt flashing correctly, i had nothing to lose After formatting it t

No, i haven't formatted the flash yet, in the Uniflash Guide is a warning: http://processors.wiki.ti.com/index.php/CC31xx_%26_CC32xx_UniFlash#Format

Reinstalling didn't help, trying to flash looks like this. I have enabled extra debug informations. [20:54:08] Begin Program operation. [20:54:08] INFO: > Executing Operation: Connect [20:54:08] DEBUG: waiting and clearing uart rx buffer [20:54:10] INFO: setting break signal [20:54:10] INFO: --- please restart the device --- [20:54:10] DEBUG: wait for ack [20:54:16] INFO: connection succeeded [20:54:16] INFO: getting storage list [20:54:16] DEBUG: wait for ack [20:54:16] INFO: > Executing Operation: Init [20:54:16] INFO: reading version info [20:54:16] DEBUG: wait for ack [20:54:16] IN

Hmm, same Version and OS here... lets reinstall this little bugger.

Yes, i did, otherwise uniflash doesn't even detect the launchpad. I'll try later a different computer / OS, perhaps its a problem of the uniflash windows version or win7 64 bit.