Main Site Documentation

Unable to call WebSite using HttpS


#1

Hello all,

I know this topic already exist, but I’m stuck with this problem since more than one month.
I’ve seen a lot of post in this forum and researching on google without any success to solve my problem.

I would like to call an HTTPs web service to use some Microsoft Azure Service with my .Net Gadgeteer.

I’ve bought a FEZ Spider Starter Kit in Feb 2014 and start to use it only in sept.

I’ve found many example on internet and finally get the sample in the “Documents\Microsoft .NET Micro Framework 4.3\Samples\HttpClient” folder.

The exception occurs here :

try
            {
                resp = request.GetResponse(); //occurs here
            }
            catch (Exception e)
            {
                Debug.Print("Exception in HttpWebRequest.GetResponse(): " + 
                    e.ToString());
            }

and the error is :
[ul][quote]Microsoft.SPOT.Net.Security.SslNative::SecureClientInit
Microsoft.SPOT.Net.Security.SslStream::Authenticate
Microsoft.SPOT.Net.Security.SslStream::AuthenticateAsClient
System.Net.HttpWebRequest::EstablishConnection
System.Net.HttpWebRequest::SubmitRequest
System.Net.HttpWebRequest::GetResponse
HttpClientSample.MyHttpClient::Main
TestWebClient.Program::Program[/ul]Started[/quote]

I’ve change the certificate because the one present in the sample seems to be outdated.
I’ve try to update the seed with FEZ Config but nothing appens when we click on the button (I’ve installed the latest version R5 just a couple of minutes ago).

I’ve updated the bootloader and the firmware since the first use.
I’ve now :
Loader (TinyBooter) : 4.3.4.0
Firmware (TinyCLR) : 4.3.6.0

My computer is on Windows 8 and I develop using VS 2012 (I’ve done the update of the loader using another computer on Win 7 because it seems to not working on Win8)

Any idea to solve this problem ? Because of that I can’t do anything with this device.

Thanks a lot.

Best Regards.

Jérémie DEVILLARD
MVP Integration - Connected System Developer http://jeremiedevillard.wordpress.com
@ jeremiedev
France


#2

@ jdevillard - Could you try to update the SSL seed using MFDeploy?


#3

When I try to update seed using MFDeploy (in C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.3\Tools), I’ve got an
Failure - Device {0} is invalid or not responding


#4

and what does Device Manager show at that point ? That kind of error is often a sign that the application is consuming the processor to the point where the debugging threads that MFDeploy connects to, to action your requests, don’t get sufficient allocation. You might try deploying a simpler app initially (blink-a-LED) to see if that changes the behaviour


#5

The device manager show the EMX device.

and I retry after deploying this sample code :

public partial class Program
    {
        public bool ledStatus =true;

        // This method is run when the mainboard is powered up or reset.   
        void ProgramStarted()
        {
            Debug.Print("Program Started");

            GT.Timer timer = new GT.Timer(1000);
            timer.Tick += timer_Tick;
            timer.Start();
        }

        void timer_Tick(GT.Timer timer)
        {
            ledStatus = !ledStatus;
            Mainboard.SetDebugLED(ledStatus);
        }
    }

with the same result :frowning:

I’ve try to erase the device using MFDeploy, I’ve got the following log :

[quote]Created EE.
Started Hardware.
Create TS.
Loading start at a0e00000, end a0e2f494
Assembly: mscorlib (4.3.1.0) Assembly: Microsoft.SPOT.Native (4.3.1.0) Assembly: Microsoft.SPOT.Security.PKCS11 (4.3.1.0) Assembly: System.Security (4.3.1.0) Assembly: Microsoft.SPOT.Hardware (4.3.1.0) Assembly: Microsoft.SPOT.Graphics (4.3.1.0) Assembly: Microsoft.SPOT.TinyCore (4.3.1.0) Assembly: Microsoft.SPOT.IO (4.3.1.0) Assembly: System.IO (4.3.1.0) Assembly: Microsoft.SPOT.Hardware.Usb (4.3.1.0) Assembly: Microsoft.SPOT.Hardware.SerialPort (4.3.1.0) Assembly: Microsoft.SPOT.Touch (4.3.1.0) Assembly: Microsoft.SPOT.Ink (4.3.1.0) Assembly: Microsoft.SPOT.Hardware.PWM (4.3.1.0) Loading Deployment Assemblies.
Resolving.
GC: 1msec 21708 bytes used, 7317960 bytes available
Type 0F (STRING ): 24 bytes
Type 15 (FREEBLOCK ): 7317960 bytes
Type 17 (ASSEMBLY ): 21180 bytes
Type 28 (MEMORY_STREAM_HEAD ): 36 bytes
Type 29 (MEMORY_STREAM_DATA ): 396 bytes
Type 34 (APPDOMAIN_HEAD ): 72 bytes
GC: performing heap compaction…
Ready.
Cannot find any entrypoint!
Done.
Waiting for debug commands[/quote]

is anything seems to be wrong?