256 replies to this topic

[piwi]

Ehm, found some rather irritating document @ http://www.ti.com/li...4b/swrz044b.pdf

 

it states that UDP broadcast does not work and will be fixed in release V1.11 but in the table it is mentioned under the column for V1.11 it does not apply ????

[baxter]

I read it to not fixed V1.11. It looks like UDP is a "work in progress" ... real bummer.

[piwi]

Yep, that's how I understood it as well. On the other hand, it could mean that the topic does not apply anymore since it has been resolved in the corresponding release.

 

Anyway, since I do have a 1.19 patch boost laying around I'll try and hope for the best .... The embedded adventures ones are at 1.10 so they need a patch ... see how I convince them of 19 ... maybe the music from Paul does help .... 

 

 

 

Release Package vs. Firmware Version

Release Package Service Pack Version

1.11   1.19

1.10.2    1.14

1.10.1  1.10

1.10   1.8

1.9  1.7

1.7.2.2 1.5

[piwi]

Well, I've seemed to have succeeded in bricking my N+. No matter what I do and with what tool MFDeploy, STDFU Tester or anything else all comes down to

 

[color=rgb(255,0,0);]Error: Can not connect to device[/color]

 

 

And exactly than when I run an update to 4.2.2.2 ..... shoot ....

 

This in the end since the build in Network did send out a UDP packet to my computer but not to 239.255.255.250:1900 and neither did the CC3000 with patch 19 allthough I got a different reaction ... something about some payload being handled ... 

[baxter]

Post to TI SimpleLink WiFi Forum:---------------------------------Does, "Does not apply" in this document mean not fixed? Specifically, Items 2.5, 2.8, 2.9 of Table 1. http://www.ti.com/lit/er/swrz044b/swrz044b.pdf Can a TI employee comment on the current functionality of UDP with the CC3000?Reply from TI-------------Hi Bruce, "Does not apply" means that issue does not apply to that service pack. Meaning it is fixed for that service pack.Regards, Aaron

It's pretty hard to brick a Netduino unless you put >5V where it does not belong. I would just repeat the flashing of the new software. I have never had a problem by following the instructions. I always reboot my PC before flashing. Sometimes, just erasing the deployed program with MFDeploy and redeploying works for me.

[Valkyrie-MT]

I have published the latest version to Codeplex.  It is located here:  http://cc3000.codeplex.com/

 

The published version has a working Udp example that sends and receives and a simple web server sample.  And there are no memory leaks

[hanzibal]

Wow!

[piwi]

I have published the latest version to Codeplex.  It is located here:  http://cc3000.codeplex.com/

 

The published version has a working Udp example that sends and receives and a simple web server sample.  And there are no memory leaks

 

Awesome ... you just made my day .... I have to try ...

 

Does the code work with other hw as well ?

 

@Bruce, that's what is happening it gives with MFDeploy and the STDUse tools from STM this can not ... message, I'm not even capable of getting any data to the N+ ... MFDeploy issues something on a memory not being addressable while deploying.

 

and thanks for the clarifying answer quote from TI ...

 

To Be Continued ...

[Valkyrie-MT]

Does the code work with other hw as well ?

 

 

Yes, it should work with any .NET MF device and any cc3000 as long as it's hooked up via the usual SPI.  I have tested on the Netduino Plus Classic, the Netduino Plus 2, and a CerbuinoBee.  All work.  My biggest concern though at this point is being able to update the firmware.  I think that could be a BIG problem...  Hopefully, we start seeing the v1.11 firmware on the newly released hardware...

[piwi]

Yes, it should work with any .NET MF device and any cc3000 as long as it's hooked up via the usual SPI.  I have tested on the Netduino Plus Classic, the Netduino Plus 2, and a CerbuinoBee.  All work.  My biggest concern though at this point is being able to update the firmware.  I think that could be a BIG problem...  Hopefully, we start seeing the v1.11 firmware on the newly released hardware...

 

I bought the CC3000s from Non-TI party in the beginning of the month and they were still on patch 10. Since I have an MSP2553G2, Stellaris and the FRAM, I can choose which MCU to use for updating the CC3000 but I guess that is not an option for everyone nor is this the way one wants to go ... I'm on my way to my lab and can't hardly wait for trying out the new S/W ....

[baxter]

Valkyrie-MT, this is a major step forward ... when do you sleep?
After a couple of abortive attempts at getting things going on MF 4.2, I have the new software running on a Plus 2

CC3000 Web Server Example ApplicationSending - Simple Link StartSend 4000 startingResponse Received -- Simple Link Start ConfirmedSetting Event MaskSend 0008 startingResponse Received -- Event Mask confirmedRequesting SP VersionSend 0207 startingResponse Received -- SP Version is 0.6.1.10Requesting Buffer SizeSend 400B startingResponse Received -- Buffer Available: 6, Size: 1500Configuring DHCPSend 2001 startingResponse Received -- DHCP Configured. The thread '<No Name>' (0x4) has exited with code 0 (0x0).Resetting Connection before setting Policy. Send 0002 startingConnection Disconnect.Setting Connection Policy.Send 0004 startingResponse Received -- Connection Policy SetAttempting Connection to tplinkSend 0001 startingWLAN Connection Established!  Waiting for IP assignment from router... IP Address Acquired => 192.168.0.130Requesting Network Connection details...Send 2005 startingWoot!  We are now connected to Wifi!Network Name: tplinkIP address: 192.168.0.130MacAddress: 08002801B2C1Gateway: 192.168.0.1DNS Server: 192.168.0.1Opening TCP SocketSend 1001 startingAcknowledged Socket Command: 040110050000000000Socket ID is 0Send 1002 startingAcknowledged Bind SuccessSend 1006 startingHandling Response for OpCode: 1006, Payload: 040610050000000000Send 1005 starting040510110000000000FEFFFFFF0200000000000000......<Debug Stopped>

Typing 192.168.0.130 in browser gives display:

 

[color=rgb(255,0,0);]The CC3000 Managed Driver
for .NET MicroFramework[/color]

[color=rgb(255,0,0);]This is just the beginning [/color]

[color=rgb(255,0,0);]Visit us at Codeplex![/color]

 

[color=rgb(0,0,0);]InternetTimeExample is a bit more problematic. "Send 100D starting" keeps repeating and doesn't seem to connect to the time server. This may have something to do with the CC3000 firmware version. I am going to try to load the V1.11 update to my CC3000 via the MSP430G2553 patch programmer[/color]
 

CC3000 Internet Time ExampleSending - Simple Link StartSend 4000 startingResponse Received -- Simple Link Start ConfirmedSetting Event MaskSend 0008 startingResponse Received -- Event Mask confirmedRequesting SP VersionSend 0207 startingResponse Received -- SP Version is 0.6.1.10Requesting Buffer SizeSend 400B startingResponse Received -- Buffer Available: 6, Size: 1500Configuring DHCPSend 2001 startingResponse Received -- DHCP Configured. The thread '<No Name>' (0x4) has exited with code 0 (0x0).Resetting Connection before setting Policy. Send 0002 startingConnection Disconnect.Setting Connection Policy.Send 0004 startingResponse Received -- Connection Policy SetAttempting Connection to tplinkSend 0001 startingWLAN Connection Established!  Waiting for IP assignment from router... IP Address Acquired => 192.168.0.130Requesting Network Connection details...Send 2005 startingWoot!  We are now connected to Wifi!Network Name: tplinkIP address: 192.168.0.130MacAddress: 08002801B2C1Gateway: 192.168.0.1DNS Server: 192.168.0.1Opening UDP SocketSend 1001 startingAcknowledged Socket Command: 040110050000000000Socket ID is 0Send 1002 startingAcknowledged Bind SuccessSend 1002 startingAcknowledged Bind SuccessSend 1883 startingSend 100D startingAcknowledged Recv SuccessData Received -- Socket Message Received040D100D00000000003000000001000000Send 100D startingSend 100D startingSend 100D starting.........

[color=rgb(0,0,0);]A couple of other observations:[/color]

[color=rgb(0,0,0);](1) After running the time server example, the web app has trouble starting again. Several restarts are necessary to get it going.[/color]

[color=rgb(0,0,0);](2) The browser is only able to connect once after stopping debug. Ping is still alive, however.[/color]

 

[piwi]

@Baxter: can only confirm. One time call of web, try a refresh (f5) and same as said above .....

 

About the UDP ... I try to send on a multicast address 239.255.255.250 message is send but can't see. if I do the same message from a pc than I do see the message.

 

However, I do get the answer back, because I listen on UDP port 1900 and in this way am turning in a control point of GENA notification message (simple http header and more...) 

 

Have to get all the boards meet with a power cycle and than runs once afterwards an infinitive loop as you stated above ... 

[piwi]

ha ... finally got the answer back and it is quite a very long list I've commented the s.StopListing() so it kinda goes on forever.

 

I got this only thru power cycling, unplugging .... and using not my finest english ....

 

Once in a redeploy I even pressed the reset on the cerbuinobee and got me a nice BSOD on my pc ... whow ... and I thought they got lost, haven't seen those for a very long time ....

 

Anyway the data list and this list goes very long so I shortened it a bit:

CC3000 UDP ExampleSending - Simple Link StartSend 4000 startingResponse Received -- Simple Link Start ConfirmedSetting Event MaskSend 0008 startingResponse Received -- Event Mask confirmedRequesting SP VersionSend 0207 startingResponse Received -- SP Version is 0.6.1.19Requesting Buffer SizeSend 400B startingResponse Received -- Buffer Available: 6, Size: 1500Configuring DHCPSend 2001 startingResponse Received -- DHCP Configured. The thread '<No Name>' (0x3) has exited with code 0 (0x0).Resetting Connection before setting Policy. Send 0002 startingConnection Disconnect.Setting Connection Policy.Send 0004 startingResponse Received -- Connection Policy SetAttempting Connection to AK16-USSend 0001 startingWLAN Connection Established!  Waiting for IP assignment from router... IP Address Acquired => 192.168.39.19Requesting Network Connection details...Send 2005 startingWoot!  We are now connected to Wifi!Network Name: AK16-USIP address: 192.168.39.19MacAddress: 08002856D381Gateway: 192.168.39.123DNS Server: 192.168.39.123Opening UDP SocketSend 1001 startingAcknowledged Socket Command: 040110050000000000Socket ID is 0Send 1002 startingAcknowledged Bind SuccessSend 1002 startingSending message to ... Acknowledged Bind SuccessSend 100D startingSend 1883 startingAcknowledged Recv SuccessData Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 192.168.39.123:1900Handling Response for OpCode: 100F, Payload: 040F1009000000000053010000	NOTIFY * HTTP/1.1Host:239.255.255.250:1900NT:urn:schemas-upnp-org:service:WANIPConnection:1NTS:ssdp:aliveLocation:http://192.168.39.123:80/igd.xmlUSN:uuid:00000000-0000-0001-0002-0012bf41a5c4::urn:schemas-upnp-org:service:WANIPConnection:1SERVESend 100D startingAcknowledged Recv SuccessData Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 110.101.99.116:12557	R: Sinus-154DSL-Bas/1.0 UPnP/1.0Cache-Control:max-age=60NOTIFY * HTTP/1.1HOST: 239.255.255.250:1900NT: upnp:rootdeviceNTS: ssdp:aliveCACHE-CONTROL: max-age=120USN: uuid:73796E6F-6473-6D00-0000-0011320de23c::upnp:rootdeviceSERVER: Synology040D100D00000000000001000001000000Send 100D startingAcknowledged Recv Success040D100D00000000000001000001000000Data Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 83.69.82.86:21369	/DSM/192.168.39.241LOCATION: http://192.168.39.241:5000/ssdp/desc-DSM-eth1.xmlOPT: "http://schemas.upnp.org/upnp/1/0/"; ns=0101-NLS: 1BOOTID.UPNP.ORG: 1CONFIGID.UPNP.ORG: 1337tO{w<Td(M{wxi{w{w`Q{w|kwSend 100D startingAcknowledged Recv Success040D100D00000000000001000001000000Data Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 123.247.224.209:27639	O{wpzwzw0zwzwP`Q{w%%{w%W{wTM{wTM{wQiw3?ow`zwP{wP{wQiw`Q{wzw0zwzwP`Q{wPUdpTd=zwpjwPPUd(Ud5{wtO{wtO{wVdT>zw`Q{wtV{w zw`QSend 100D startingAcknowledged Recv Success040D100D00000000000001000001000000Data Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 0.0.0.0:31479	{w[Vh+0T{w8zw@Y{w@Y{wHT{wUMh+HT{wp{wtO{wYd,Xd(b{w4LVdRVd zw40LiSend 100D startingAcknowledged Recv Success040D100D00000000000001000001000000Data Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 0.0.7.0:1032	nuxNOTIFY * HTTP/1.1Host:239.255.255.250:1900NT:urn:schemas-upnp-org:service:WANPPPConnection:1NTS:ssdp:aliveLocation:http://192.168.39.123:80/igd.xmlUSN:uuid:00000000-0000-0001-0002-0012Send 100D startingSend 100D startingAcknowledged Recv Success040D100D00000000000001000001000000Data Received -- Socket Message Received08/21/2013 00:00:00 - receiving message from 48.45.48.48:12336	bf41a5c4::urn:schemas-upnp-org:service:WANPPPConnection:1SERVER: Sinus-154DSL-Bas/1.0 UPnP/1.0Cache-Control:max-age=60NOTIFY * HTTP/1.1HOST: 239.255.255.250:1900NT: upnp:rootdeviceNTS: ssdp:aliveCACHE-CONTROL: max-age=120USN: uuid:73796E6

[baxter]

@piwi, This is encouraging. You got UDP to work. Your SP version is 0.6.1.19 and mine is 0.6.1.10; Looks like I must update my CC3000. All of this going back to the TI platforms for firmware updating is distasteful to say the least. I bought the Embedded Adventures MCP2210 USB2SPI Module  (http://www.embeddeda...spi_module.html) with the thought to do the updating via a PC. The update files are just hex text files and the CC3000 doesn't care what it is connected to as long as the signal lines are preserved. Microchip has a lot of good support software (DLL, configuration utility, terminal ...). The main problem is digging out the proper sequence of SPI commands/response for patch programming.

[piwi]

OTA patching would be very nice.

 

I've not looked into this, but does the boost do not have the I2C pins where patching can be done. Maybe there is a way of connecting the I2C to the N+ and run the patching sourced from some hex files residing on a sd-card. One might even think of auto detecting there are patch files found and the system kind of patches automatically or by some sequence of some kind.

 

Like pulling your left ear twice and blink three times with your right eye and than the patching takes off ... kinda ...

[Valkyrie-MT]

The driver library made it to Hack-a-Day!

 

http://hackaday.com/...for-net-micros/

[baxter]

@Valkyrie-MT: Congratulations ... The only Hackers that get on Hack a Day are doing important, interesting work.

 

I have 2 Embedded Adventures WRL-3000V2 modules. One was updated to firmware V1.11 and the other, as delivered. When I run your V4 (on CodePlex) software, both give the following output and freeze at "Send 0002 starting". I think both are bad because they give no response at all compared with my post, #191. For the output in #191, I was using a module from a Parallax seller.

CC3000 Web Server Example ApplicationSending - Simple Link StartSend 4000 starting<----Missing Response Received -- Simple Link Start Confirmed ---->Setting Event MaskSend 0008 startingRequesting SP VersionSend 0207 startingResetting Connection before setting Policy. Send 0002 startingHangs in: internal byte[] Send(byte[] theCommand, uint timeout = 2000)VS Break all: --> lock (lockVar)

Out of 5 modules (2 Boost, 2 WRL-3000V2 and 1 Parallax), the Parallax is the only one that works. The 2 Boost modules also basically give the same output as above. It would almost seem that TI let some bad CC3000 chips into the pipeline. I contacted TI about my first Boost with the claim that it was bad. They sent a new one and curiously it has a TI label with a MAC address. There is also a label on top of the CC3000 chip with a FCC ID number and a series of 8, 2 digit numbers separated by colons.

 

I am going back to the MSPG2553+Boost to see if I can get it setup with the OTA First Time Configuration, http://processors.wi...n#Using_Beacons

If I can't then there is something dreadfully wrong and I will just put this aside until TI can get its act together.

[piwi]

Hi Baxter, welcome to the club.

 

I have got two CC3000 Boost both on patch 19. The one works pretty much constantly and can even handle UDP packets. The other one, as well on patch 19 gives me the creeps though. Sofar not succeeded in coming even close to the first one ?????? 

 

If I use the second on a TI Sellaris board it just connects and get's an IP address, wunderfull, unsecured but working. But when I exchange the first one with the second one and you would think, same setup, same patch, same power supply and same software, well nothing is more surprising then good old TI always open for a surprise...it just doesn't ....... work. Although this one is secured thru WPA/WPA2 etc.

CC3000 Web Server Example ApplicationSending - Simple Link StartSend 4000 startingSend 4000 startingSend 4000 startingSend 4000 startingSetting Connection Policy.Send 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingSend 4000 startingSend 0004 startingAttempting Connection to AK16-USSend 0001 startingSetting Event MaskSend 0008 startingRequesting SP VersionSend 0207 startingRequesting Buffer SizeSend 400B startingConfiguring DHCPSend 2001 starting

beats me ....

[baxter]

To further compound the mystery, I hooked up my original Boost(V1.11, patch 19 alleged to be non-functional by me) to the MSP430G2553. The MSP430 was loaded with the binary from the V1.11 SDK. The reset button on the MSP was pressed. The following is what I did:

Conditions----------Static IP = C0a8002d (192.168.0.45)--> For C3000 Gateway   = C0a80001 (192.168.0.1) Main routerGateway   = C0A800fe (192.168.0.254) tplink attached to main router (open sec.)Main router DHCP range = 100-254Command sequence followed: (Static Configuration, connect to tplink)--------------------------------------------------------------------0a <-- clear previous09 <-- disconnect08c0a8002dc0a800fe <-- set static IP address and gateway (tplink)026tplink0 <-- connect to tplink, open security(0)Executing commands on a serial terminal(9600 baud) --> MSP430:--------------------------------------------------------------Press reset on MSP430G2553 --> Example App:driver version 2.13.7.130a --> DONE09 --> Illegal command DONE08c0a8002dc0a800fe --> Illegal commandDONEPress reset on MSP430G2553 --> Example App:driver version 2.13.7.1308c0a8002dc0a800fe --> DONE026tplink0 --> Illegal commandDONEPress reset on MSP430G2553 --> Example App:driver version 2.13.7.13026tplink0 --> DONE IP:192.168.0.45 <-- What we want(N.B. a MSP430 reset after the last command will require a reissue of command:026tplink0)Commands on PC--------------C:UsersbebDesktop>ping 192.168.0.45Pinging 192.168.0.45 with 32 bytes of data:Reply from 192.168.0.45: bytes=32 time=5ms TTL=64Reply from 192.168.0.45: bytes=32 time=3ms TTL=64Reply from 192.168.0.45: bytes=32 time=3ms TTL=64Reply from 192.168.0.45: bytes=32 time=3ms TTL=64Ping statistics for 192.168.0.45:    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 3ms, Maximum = 5ms, Average = 3msC:UsersbebDesktop>arp -aInterface: 192.168.0.106 --- 0xb  Internet Address      Physical Address      Type  ...			...			...  192.168.0.45          00-12-55-55-55-55     dynamic  <--MSP430+CC3000 (MAC needs to be  set, not TI OUI)  ...			...			...  192.168.0.254         64-70-02-32-6e-38     dynamic  <-- tplink  ...	

So, my bad CC3000 Boost is not bad; it can be given a static IP address and connected to a TP-Link with open security. it will not , however, run with Valkyrie-MT's code. I was unsuccessful with a OTA Smart_Link configuration. The TI iPad App somehow took the SSID of my main network and won't let me change it. When I get around to it I will try the TI PC Java App.

 

The CC3000 is an innovative product, but something is truly screwed up. It has been on the market for well over a year and a lot of smart embedded developers are working on it.  However, no full featured implementations/products exist. The Adafruit and Embedded Adventures offerings are only partial with promises of more to come. I started this thread with the hope that we could adapt it to the Netduino Mini , but my hopes are rapidly fading. For the Netduino Plus and Plus 2 , the Edimax BR-6258n NANO is the perfect solution (in my opinion) for wireless connectivity. It fits on a protoshield and when configured as an ethernet/wireless adapter it works transparently; no driver code necessary and existing networking code works flawlessly as if hooked to the network via an ethernet cable. Moreover, it draws about the same power as the CC3000.

Edit: Maybe another partial implementation; anyone for Javascript with the CC3000?

http://technical.io/...bf6c0b-44060589

[Valkyrie-MT]

I just bought a new cc3000 chip with the new symbolization, but it had the old firmware.  So, I decided this weekend to start work on a C# based firmware flasher.  Nearly all the code is done, but it likely has bugs, but I am going to test extensively before I try anything on my guinea pig cc3000.  Also, I have added several key tests in the initialization to give useful errors when the communications are not working...  This will easily enable a remote update because the patch location can be anywhere.