Look what I’ve found on my door steps, my dose of Oxygen and Neon 
Let’s hope @ Justin doesn’t cover where the leak came from :whistle: As I’m afraid I will get hooked and will definitely require an ongoing doses.
Jay
3 Likes
Since we are talking about molecules anyway, what is wrong with the Neon, it stopped working at some point :whistle:
@ peter, shouldn’t you be under the Radar as @ Justin might just figure out who the leaker is :whistle:
aren’t you missing an 8 legged spider in there :wall:
jay
@ JayJay - and the new 32 MBit spider didn’t want to sync … :wall: :wall:
… stupid me, and no comments please, forgot to ground the programming connection. Now I got the latest AT firmware on the neon. :dance:
Yoohoo, got the neon to have a little bit more flash … 32MBit. With an upgraded Oxygen to Netmf 4.4 and the neon at 1.5.1 (or AT 0.52.0.0) I ran some sample software and voila it worked …
Kudos to @ mcalsyn for making this wunderfull piece of software and of course not to forget kudos to our marvelous @ Justin …
Found debugger!
Create TS.
Loading start at 8045e7c, end 805ae3c
Assembly: mscorlib (4.4.0.0) Assembly: Microsoft.SPOT.Native (4.4.0.0) Assembly: Microsoft.SPOT.Hardware (4.4.0.0)
Assembly: Microsoft.SPOT.Hardware.Usb (4.4.0.0) Assembly: Microsoft.SPOT.Hardware.SerialPort (4.4.0.0)
Assembly: Windows.Devices (4.4.0.0) Assembly: Microsoft.SPOT.Time (4.4.0.0)
Loading Deployment Assemblies.
Attaching deployed file.
Assembly: System (4.4.0.0) Attaching deployed file.
Assembly: PervasiveDigital.Diagnostics (3.0.2.0) Attaching deployed file.
Assembly: PervasiveDigital.Hardware.ESP8266 (3.0.2.0) Attaching deployed file.
Assembly: PervasiveDigital.Utility (3.0.2.0) Attaching deployed file.
Assembly: OxyNeonPd44 (1.0.0.0) Attaching deployed file.
Assembly: Microsoft.SPOT.Net (4.4.0.0) Attaching deployed file.
Assembly: PervasiveDigital.Net (3.0.2.0) Resolving.
The debugging target runtime is loading the application assemblies and starting execution.
Ready.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Native.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Hardware.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Windows.Devices.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Time.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\Microsoft.SPOT.Net.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.4\Assemblies\le\System.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Users\peter\Documents\vs15\Projects\OxyNeonPd44\packages\PervasiveDigital.Utility.3.0.2-beta\lib\netmf44\le\PervasiveDigital.Utility.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Users\peter\Documents\vs15\Projects\OxyNeonPd44\packages\PervasiveDigital.Diagnostics.3.0.2-beta\lib\netmf44\le\PervasiveDigital.Diagnostics.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Users\peter\Documents\vs15\Projects\OxyNeonPd44\packages\PervasiveDigital.Net.3.0.2-beta\lib\netmf44\le\PervasiveDigital.Net.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'C:\Users\peter\Documents\vs15\Projects\OxyNeonPd44\packages\PervasiveDigital.Hardware.ESP8266.3.0.2-beta\lib\netmf44\le\PervasiveDigital.Hardware.ESP8266.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'Microsoft.SPOT.Debugger.CorDebug.14.dll' (Managed): Loaded 'c:\users\peter\documents\vs15\Projects\OxyNeonPd44\OxyNeonPd44\bin\Debug\le\OxyNeonPd44.exe', Symbols loaded.
ThreadPool thread created: #1
ThreadPool thread created: #2
ThreadPool thread created: #3
The thread '<No Name>' (0x2) has exited with code 0 (0x0).
Received : sl
Received : ready
Sent command : AT
Received : AT
Received : OK
Consumed: AT
Consumed: OK
Sent command : ATE0
Received : ATE0
Received : OK
Consumed: ATE0
Consumed: OK
Sent command : AT+CIPMUX=1
Received : OK
Consumed: OK
Sent command : AT+GMR
Received : AT version:0.52.0.0(Jan 7 2016 18:44:24)
Received : SDK version:1.5.1(e67da894)
Received : compile time:Jan 7 2016 19:03:30
Received : OK
Consumed: AT version:0.52.0.0(Jan 7 2016 18:44:24)
Consumed: SDK version:1.5.1(e67da894)
Consumed: compile time:Jan 7 2016 19:03:30
Consumed: OK
Sent command : AT+CWMODE=1
Received : OK
Consumed: OK
Access points:
Sent command : AT+CWLAP
Received : +CWLAP:(4,"XXX",-77,"f8:1a:67:7e:21:c3",6,26,0)
Received : +CWLAP:(4,"YYY",-81,"00:22:75:22:44:f4",13,13,0)
Received : +CWLAP:(3,"ZZZ",-82,"00:22:75:22:44:f5",13,13,0)
Received : OK
Consumed: +CWLAP:(4,"XXX",-77,"f8:1a:67:7e:21:c3",6,26,0)
Consumed: +CWLAP:(4,"YYY",-81,"00:22:75:22:44:f4",13,13,0)
Consumed: +CWLAP:(3,"ZZZ",-82,"00:22:75:22:44:f5",13,13,0)
Consumed: OK
ssid:"TheOne" ecn:4
ssid:"GoForSecond" ecn:4
ssid:"ThreeTimesACharm" ecn:3
-- end of list -------------
Sent command : AT+CWJAP="XXX","XXX"
Received : WIFI CONNECTED
Consumed: WIFI CONNECTED
Received : WIFI GOT IP
Consumed: WIFI GOT IP
Received : OK
Consumed: OK
Sent command : AT+CIPSTA?
Received : +CIPSTA:ip:"192.168.mmm.aaa"
Received : +CIPSTA:gateway:"192.168.mmm.nnn"
Received : +CIPSTA:netmask:"255.255.255.0"
Received : OK
Consumed: +CIPSTA:ip:"192.168.mmm.aaa"
Consumed: +CIPSTA:gateway:"192.168.mmm.nnn"
Consumed: +CIPSTA:netmask:"255.255.255.0"
Consumed: OK
Station IP address : 192.168.mmm.aaa
Sent command : AT+CIPSTAMAC?
Received : +CIPSTAMAC:"aa:bb:cc:a1:58:cf"
Received : OK
Consumed: +CIPSTAMAC:"aa:bb:cc:a1:58:cf"
Consumed: OK
Station MAC address : aa:bb:cc:a1:58:cf
Station Gateway address : 192.168.mmm.nnn
Station netmask : 255.255.255.0
Sent command : AT+CIPSTART=0,"UDP","time1.google.com",123
Received : 0,CONNECT
Received : OK
Consumed: 0,CONNECT
Sent command : AT+CIPSEND=0,48
Received : OK
Consumed: OK
Received : >
Received : Recv 48 bytes
Received : SEND OK
Consumed: >
Consumed: Recv 48 bytes
Consumed: SEND OK
Reading a stream of 48 bytes for channel 0
STREAM: Copied 4 characters to stream. Buffer contains:0 Stream contains : 4 Still need:44
STREAM: Copied 44 characters to stream. Buffer contains:0 Stream contains : 48 Still need:0
Sent command : AT+CIPCLOSE=0
Received : 0,CLOSED
Received : OK
Consumed: OK
Sent command : AT+CIPSERVER=1,80
Received : OK
Consumed: OK
Sent command : AT+CIPSTART=0,"TCP","www.example.com",80
Received : 0,CONNECT
Received : OK
Consumed: 0,CONNECT
Sent command : AT+CIPSEND=0,41
Received : OK
Consumed: OK
Received : >
Received : Recv 41 bytes
Consumed: >
Consumed: Recv 41 bytes
Received : SEND OK
Consumed: SEND OK
Reading a stream of 1414 bytes for channel 0
STREAM: Copied 2 characters to stream. Buffer contains:0 Stream contains : 2 Still need:1412
STREAM: Copied 86 characters to stream. Buffer contains:0 Stream contains : 88 Still need:1326
STREAM: Copied 79 characters to stream. Buffer contains:0 Stream contains : 167 Still need:1247
STREAM: Copied 77 characters to stream. Buffer contains:0 Stream contains : 244 Still need:1170
STREAM: Copied 75 characters to stream. Buffer contains:0 Stream contains : 319 Still need:1095
STREAM: Copied 164 characters to stream. Buffer contains:0 Stream contains : 483 Still need:931
STREAM: Copied 114 characters to stream. Buffer contains:0 Stream contains : 597 Still need:817
STREAM: Copied 270 characters to stream. Buffer contains:0 Stream contains : 867 Still need:547
STREAM: Copied 382 characters to stream. Buffer contains:0 Stream contains : 1249 Still need:165
STREAM: Copied 165 characters to stream. Buffer contains:213 Stream contains : 1414 Still need:0
Reading a stream of 200 bytes for channel 0
STREAM: Copied 200 characters to stream. Buffer contains:0 Stream contains : 200 Still need:0
==== Response received ================================
Status : 200
Reason : OK
Cache-Control : max-age=604800
Server : ECS (iad/182A)
Accept-Ranges : bytes
X-Cache : HIT
Date : Sun, 07 Feb 2016 15:04:39 GMT
Content-Length : 1270
Expires : Sun, 14 Feb 2016 15:04:39 GMT
Vary : Accept-Encoding
Content-Type : text/html
x-ec-custom-error : 1
Etag : "359670651"
Last-Modified : Fri, 09 Aug 2013 23:54:35 GMT
Body:
<!doctype html>
<html>
<head>
<title>Example Domain</title>
<meta charset="utf-8" />
<meta http-equiv="Content-type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<style type="text/css">
body {
background-color: #f0f0f2;
margin: 0;
padding: 0;
font-family: "Open Sans", "Helvetica Neue", Helvetica, Arial, sans-serif;
}
div {
width: 600px;
margin: 5em auto;
padding: 50px;
background-color: #fff;
border-radius: 1em;
}
a:link, a:visited {
color: #38488f;
text-decoration: none;
}
@ media (max-width: 700px) {
body {
background-color: #fff;
}
div {
width: auto;
margin: 0 auto;
border-radius: 0;
padding: 1em;
}
}
</style>
</head>
<body>
<div>
<h1>Example Domain</h1>
<p>This domain is established to be used for illustrative examples in documents. You may use this
domain in examples without prior coordination or asking for permission.</p>
<p><a href="http://www.iana.org/domains/example">More information...</a></p>
</div>
</body>
</html>
Sent command : AT+CIPCLOSE=0
Received : 0,CLOSED
Received : OK
Consumed: OK
Current UTC time : 02/07/2016 15:04:44
Current UTC time : 02/07/2016 15:04:49
6 Likes
very cool 
so just replacing the flash chip is enough to upgrade the current ESPs at hand? can you please share the link to that chip
1 Like
@ .Peter. - Well done that man!
This is what i love about this sort of community effort, you mix an Alcoholic, an Astronaut and a Sheep herder and you come up with this sort of gem.
Forget what people say about square pegs and round holes etc, give it a go and prove people wrong.
A lot of modern electronics is relatively easy (not taking anything away from Peters magic) so like Peter, pull out the soldering iron and give it a go - you will be pleasantly surprised what you can achieve.
Again - excellent work Peter (and Martin)
2 Likes
Nicely done indeed! With all that extra memory, you might be able to pull off an OTA firmware update of the ESP now. It’s supported in the api, but I could never test it.
Because I am in transit, I can’t try it myself, but as soon as my rework station arrives in the US, I’ll give it a go.
2 Likes
@ Jay Jay - Since esp can handle up to 128MBit, I’ve ordered 32, 64, and 128 flash chips. I’ve already tried 64 on esp-01 and working with a bootable flash, still wip …
the flasher i have only goes until 32 so i took that size for the esp-03. They are all ordered from digikey. winbound. W25Q32FVSSIG-ND for the 32MBit version.
[url]http://www.digikey.com/product-search/en?keywords=w25q32fvssig-nd[/url]
[edit] watch out for the physical size these are a bit large and barely fit on the pcb landing zones of the original flash chip
1 Like
The 1.5.1 readme makes me wonder if it’ll work, but never tried …
Interesting - given that the mem issue stopped me dead, I never investigated further, but if (and when) I hack my way around that, I’ll have a play with it.
@ mcalsyn - after updating the modded ESP-03 to a bootable stand alone mode of the neon it kind of chickened out on me, can you believe that …
In other words, no OTA update yet. Nor the ESP-01 neither the Neon, both being now on the January 7th firmware …
What does comes strange to me is that in the manual/read me there should be extra comment on each update response line but I don’t get any. So I’m wondering if my ESPs do get out to the internet at all :think:
@ peter: according to the notice in this link [SDK Release] ESP8266_NONOS_SDK_V1.5.2_16_01_29 - ESP8266 Developer Zone OTA update doesn’t work right with the latest AT command
[quote]AT_v0.60 Release Note:
Notice：
2. Firmware upgrade over-the-air process is changed a bit. We will upgrade the latest AT firmware to Espressif Cloud server only after it has been tested and the overall performance is guaranteed. Users may not be able to use AT+CIUPDATE in ESP8266_NONOS_SDK_V1.5.0 and other more advanced versions.
[/quote]
Edit: I just reread your last post and you already mentioned this :wall:
Cheers,
Jay
@ Jay Jay - Better twice than no mention at all …
After updating the modded neon to AT_v0.60 it strikes me as if it somewhat more unstable. With the previous release I could hit F5 in chrome and the neon didn’t stopped working, now with 0.60 only one hit on F5 and than blinking LED stopped immediately.
The software SimpleHttpTest from [url]https://github.com/PervasiveDigital/serialwifi/tree/master/src[/url] and nuget packages v3.0.2 beta applied.
Nah, there is still to investigate if WPS and MDNS do work …
and I have already met with the fact that it is very expensive and does cost you a lot of nerve too :whistle:
There is a nice article series over the SAM D20 (shouldn’t be that far from the D21) in Elektor magazine, started in Feb 2015 and still ongoing.
Dutch → [url]https://www.elektor.nl/elektor-magazine-nl-jan-febr-2015-als-pdf[/url]
English → [url]https://www.elektor.com/elektor-magazine-en-january-february-2015-pdf[/url]
German → [url]https://www.elektor.de/elektor-01-02-2015-pdf-de[/url]