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.
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.
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.
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?
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?
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.
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.
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.
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
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.
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:
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
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
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.