Netduino home hardware projects downloads community

Jump to content


The Netduino forums have been replaced by new forums at community.wildernesslabs.co. This site has been preserved for archival purposes only and the ability to make new accounts or posts has been turned off.
Photo

Cannot find any entrypoint!


  • Please log in to reply
18 replies to this topic

#1 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 10 April 2012 - 04:27 AM

The debugger starts, then exits without hitting any breakpoints. The output window shows "Cannot find any entrypoint!"

I'm trying to work out what caused it. I've re-installed both .NetMF and NetduinoSDK. I was working happily, then took a break, and my laptop had frozen, so I restarted it, and have gotten this error since. Known working backups show the same error. But basic blinky works ok. :blink:

Micro Framework Device Deployment:

Incrementally deploying assemblies to device
Deploying assemblies for a total size of 41108 bytes
Assemblies successfully deployed to device.


Debug Output:

Found debugger!

Create TS.

Loading start at 155b88, end 16e8e0

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Attaching file.

Loading Deployment Assemblies.

Attaching deployed file.

Resolving.

The debugging target runtime is loading the application assemblies and starting execution.
Ready.

Cannot find any entrypoint!

Done.

Waiting for debug commands...

'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\mscorlib.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Native.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Net.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\System.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.PWM.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Diagnostics.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.2\le\SecretLabs.NETMF.Hardware.NetduinoPlus.dll', Symbols loaded.
The program '[1] Micro Framework application: Managed' has exited with code 0 (0x0).



#2 ErikN

ErikN

    Advanced Member

  • Members
  • PipPipPip
  • 119 posts
  • LocationNew York, NY

Posted 10 April 2012 - 05:55 AM

This is what you'll see if you don't have a proper static main() method to start/run your project. Did something happen to it?

#3 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 10 April 2012 - 06:48 AM

First thing I checked. It's there.

public static void Main()
{
...
}


#4 CW2

CW2

    Advanced Member

  • Members
  • PipPipPip
  • 1592 posts
  • LocationCzech Republic

Posted 10 April 2012 - 06:56 AM

That error can also mean the runtime cannot locate the application main assembly, for example when it was not deployed successfully. Could you please try erasing the application via 'Erase' button in MFDeploy (next to 'Ping' button) and re-deploy?

#5 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 10 April 2012 - 06:59 AM

That error can also mean the runtime cannot locate the application main assembly, for example when it was not deployed successfully. Could you please try erasing the application via 'Erase' button in MFDeploy (next to 'Ping' button) and re-deploy?


I'll try that when I get back home, what I did already try was a full erase, reload tinybootloader, RC4 and I got the same issue. If VS states "Assemblies successfully deployed to device." does it really mean it?

#6 Dan Morphis

Dan Morphis

    Advanced Member

  • Members
  • PipPipPip
  • 188 posts

Posted 10 April 2012 - 05:12 PM

I'll try that when I get back home, what I did already try was a full erase, reload tinybootloader, RC4 and I got the same issue. If VS states "Assemblies successfully deployed to device." does it really mean it?


You don't by chance have multiple projects loaded in your solution do you? If you have multiple projects in a solution, everyone of them gets deployed to your board, and then its luck of the draw as to which one actually gets executed.

-dan

#7 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 10 April 2012 - 07:32 PM

Could you please try erasing the application via 'Erase' button in MFDeploy (next to 'Ping' button) and re-deploy?


I erased the program, and deployed again; no change.

You don't by chance have multiple projects loaded in your solution do you?


Only the one project in the solution, I also tried creating a new solution altogether and replacing the Program.cs file.

I'm thinking this has something to do with my machine, but if the blinky test works..

#8 Paul Csiki

Paul Csiki

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationDublin, Ireland

Posted 11 April 2012 - 10:20 AM

Have you tried adding a breakpoint to see if breaks?

#9 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 11 April 2012 - 10:29 AM

Have you tried adding a breakpoint to see if breaks?


Yeah. I tried a break point on Main, and on the first declaration as well. Never hits.
I've also now tried on a second machine - so it's not specific to my machine.

#10 Paul Csiki

Paul Csiki

    New Member

  • Members
  • Pip
  • 8 posts
  • LocationDublin, Ireland

Posted 11 April 2012 - 10:50 AM

I couldn't help to notice that you are using .NET MF 4.2, can you switch back to stable 4.1 and see if you can replicate the problem?

#11 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 April 2012 - 08:27 PM

I couldn't help to notice that you are using .NET MF 4.2, can you switch back to stable 4.1 and see if you can replicate the problem?

Also...did you make any changes recently (before this stopped working)?

When you updated to .NET MF 4.2, did you reflash TinyBooter...and then flash the matching TinyCLR (.NET MF firmware)?

There are a few reasons you could get this error. The most common:
  • No startup project and/or routine
  • Flash memory layout mismatch
  • Worn out flash (not likely)

Do you have another board to test the app on?

Chris

#12 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 11 April 2012 - 08:43 PM

Also...did you make any changes recently (before this stopped working)?

No changes.

When you updated to .NET MF 4.2, did you reflash TinyBooter...and then flash the matching TinyCLR (.NET MF firmware)?

I did. I flashed TinyBooterDecompressor.bin from Firmware_NetduinoPlus_4.2.0.0_RC4 using SAMBA

There are a few reasons you could get this error. The most common:

  • No startup project and/or routine
  • Flash memory layout mismatch
  • Worn out flash (not likely) <-- I'm going with this option.


Do you have another board to test the app on?

I do, tested on second board with the same solution - unplugged problem Netduino, plugged in new Netduino and it worked straight away. I then loaded Blinky test on the problem Netduino which worked, and also tried another program with smaller size (7KB vs 40KB) that has networking and SD code, all worked happily as well. It's as if the flash works ok in the 'lower' sections, but is worn out further on.

#13 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 11 April 2012 - 08:53 PM

Hi Colin, I wish you were closer, I'd give you a trophy and a free Netduino. The SAM7X MCU on Netudino is rated for 10,000+ reflashing cycles. You've done a _lot_ of development if you've gotten that far. Impressive. I'm not sure if we've ever worn a flash sector (outside of testing scenarios). It's on the list of things that can happen, so I mentioned it, but wow... Chris
  • Arron Chapman and Paul Csiki like this

#14 ColinR

ColinR

    Advanced Member

  • Members
  • PipPipPip
  • 142 posts
  • LocationCape Town, South Africa

Posted 12 April 2012 - 03:42 AM

The SAM7X MCU on Netudino is rated for 10,000+ reflashing cycles. You've done a _lot_ of development if you've gotten that far. Impressive.


My board has been used extensively for product development, 10 000 reflashing cycles is easily possible. The current solution is on revision 4817, and I'll typically deploy 3 or 4 times at least per revision.

Time for a new Netduino!

#15 Francisco

Francisco

    New Member

  • Members
  • Pip
  • 8 posts

Posted 12 April 2012 - 08:37 PM

Hi Colin,

I wish you were closer, I'd give you a trophy and a free Netduino. The SAM7X MCU on Netudino is rated for 10,000+ reflashing cycles. You've done a _lot_ of development if you've gotten that far. Impressive.

I'm not sure if we've ever worn a flash sector (outside of testing scenarios). It's on the list of things that can happen, so I mentioned it, but wow...

Chris


Hi Chris,

I have a similar problem with my N+, the blinky program is working fine, but when I try to work with the serial ports, seems like the program hangs forever. This is what the aoutput windows says:

Rebooting...


TinyCLR (Build 4.1.2821.0)


Starting...

Found debugger!

Create TS.

Loading start at 14d324, end 162e8c

Attaching file.

Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.Net (4.1.2821.0) (704 RAM - 5060 ROM - 2452 METADATA)


Attaching file.

Assembly: System (4.1.2821.0) (872 RAM - 5992 ROM - 3206 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA)


Attaching file.

Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (512 RAM - 3488 ROM - 1543 METADATA)


Attaching file.

Assembly: Microsoft.SPOT.Hardware.Usb (4.1.2821.0) (580 RAM - 3740 ROM - 1844 METADATA)


Attaching file.

Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA)


Attaching file.

Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA)


Loading Deployment Assemblies.

Attaching deployed file.

Assembly: SimpleBCreader (1.0.0.0) (256 RAM - 808 ROM - 363 METADATA)


Attaching deployed file.

Assembly: SecretLabs.NETMF.Hardware.NetduinoPlus (4.1.0.0) (268 RAM - 816 ROM - 423 METADATA)


Resolving.


Total: (11012 RAM - 90556 ROM - 49856 METADATA)



Total: (11012 RAM - 90556 ROM - 49856 METADATA)


The debugging target runtime is loading the application assemblies and starting execution.
Ready.

'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\mscorlib.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Native.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Net.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\System.IO.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.SerialPort.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.1\Assemblies\le\Microsoft.SPOT.Hardware.Usb.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.1\le\SecretLabs.NETMF.Hardware.dll', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'SecretLabs.NETMF.Diagnostics'
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Users\Francisco Rascon\Documents\Visual Studio 2010\Projects\SimpleBCreader\SimpleBCreader\bin\Debug\le\SimpleBCreader.exe', Symbols loaded.
'Microsoft.SPOT.Debugger.CorDebug.dll' (Managed): Loaded 'C:\Program Files (x86)\Secret Labs\Netduino SDK\Assemblies\v4.1\le\SecretLabs.NETMF.Hardware.NetduinoPlus.dll', Symbols loaded.
The thread '<No Name>' (0x2) has exited with code 0 (0x0).

The next lines appear in the output windows when in the main Event reads the code: serial = new SerialPort(SerialPorts.COM1,9600);

Step into: Stepping over non-user code 'System.IO.Ports.SerialPort.SerialPort'
Step into: Stepping over non-user code 'System.IO.Ports.SerialPort.SerialPort'
Step into: Stepping over non-user code 'System.IO.Ports.SerialPort.SerialPort'

this is my full code:

using System.IO.Ports;

using Microsoft.SPOT.Hardware;
using SecretLabs.NETMF.Hardware.NetduinoPlus;
using System.Threading;


namespace SimpleBCreader
{
    public class Program
    {
        static SerialPort serial;

        public static void Main()
        {
            // write your code here
            serial = new SerialPort(SerialPorts.COM1,9600);	//Whit this line the program hangs
            serial.Handshake = Handshake.None;
            serial.Open();

            serial.DataReceived += new SerialDataReceivedEventHandler(serial_DataReceived);
            serial.ErrorReceived += new SerialErrorReceivedEventHandler(serial_ErrorReceived);

            Thread.Sleep(Timeout.Infinite);
        }

        static void serial_ErrorReceived(object sender, SerialErrorReceivedEventArgs e)
        {
            //Debug.Print(e.ToString());
        }

        static void serial_DataReceived(object sender, SerialDataReceivedEventArgs e)
        {
            //Debug.Print("Data received");
            // create a single byte array
            byte[] bytes = new byte[1];

            // as long as there is data waiting to be read
            while (serial.BytesToRead > 0)
            {
                // read a single byte
                serial.Read(bytes, 0, bytes.Length);
                // send the same byte back
                serial.Write(bytes, 0, bytes.Length);
            }
        }


    }
}
I thought that maybe my N+ was damaged, so I orderer a new One, same problem.


Please Help.

Edited by Chris Walker, 13 April 2012 - 12:14 AM.
added [quote][/quote] and [code][/code] tags


#16 Chris Walker

Chris Walker

    Secret Labs Staff

  • Moderators
  • 7767 posts
  • LocationNew York, NY

Posted 13 April 2012 - 12:16 AM

Hi Francisco, If you set a breakpoint in your main routine and then step through it, how far does it get? If you set a breakpoint in your DataReceived event, does it get tripped when you send data to your Netduino Plus? Finally...what firmware version are you running? Did you update your Netduino Plus from the stock 4.1.0.6 firmware? Chris

#17 Gutworks

Gutworks

    Advanced Member

  • Members
  • PipPipPip
  • 363 posts
  • LocationOttawa, Ontario

Posted 13 April 2012 - 12:36 AM

I'm having similar problems since flashing and moving to 4.2. I'm in the process of uninstalling .NETMF and the Netduino sdk once again to see if it makes a difference. The issue has also spilled over to my Netduino Go projects as well. I'll post my results a little later. Watching the Ottawa and New York hockey game at the moment. :)

#18 alesbedac

alesbedac

    Advanced Member

  • Members
  • PipPipPip
  • 63 posts

Posted 26 October 2013 - 08:13 PM

I get today the same bug...

 

problem was in projec tclass library where was assigned another project class library (ACL)...but this ACL was missing,

I have deleted this project from sollution, but reference wasn deleted.

 

after removing missing reference was everything OK

 

2013-10-25

sorry wrong..i have still the same error. but when is from main prohject removed one library is program working.

this library i am using for networking



#19 Lebeda

Lebeda

    New Member

  • Members
  • Pip
  • 5 posts

Posted 02 September 2014 - 06:57 AM

I got the same error when my project was targeting MF 4.3 but my Netduino2+ was running 4.2 firmware






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

home    hardware    projects    downloads    community    where to buy    contact Copyright © 2016 Wilderness Labs Inc.  |  Legal   |   CC BY-SA
This webpage is licensed under a Creative Commons Attribution-ShareAlike License.