Search found 634 matches
- Tue Feb 03, 2015 7:39 am
- Forum: NetBurner's Eclipse IDE
- Topic: Launching failure
- Replies: 17
- Views: 30589
Re: Launching failure
Not sure what you mean by "code set", but I can compile my application and the example programs. I'm using Java Standard Edition, version 8 update 31. The about dialog doesn't say whether it's 32 or 64 bit.
- Mon Feb 02, 2015 3:43 pm
- Forum: NetBurner's Eclipse IDE
- Topic: Launching failure
- Replies: 17
- Views: 30589
Launching failure
I get error ""Launching myapp has encountered a problem." Followed by message: "An internal error occurred during: Launching myapp. String index out of range: 0"
I have no idea where to go with that.
I'm using v2.7.0 of the IDE on Win7, with a NANO54415. Compiled in Debug mode. I can see the Nano ...
I have no idea where to go with that.
I'm using v2.7.0 of the IDE on Win7, with a NANO54415. Compiled in Debug mode. I can see the Nano ...
- Mon Oct 20, 2014 12:55 pm
- Forum: NetBurner Software
- Topic: Semiphore failure in v2.6.8
- Replies: 3
- Views: 3380
Re: Semiphore failure in v2.6.8
That fixed it.
Thanks much.
Steve
Thanks much.
Steve
- Mon Oct 20, 2014 11:11 am
- Forum: NetBurner Software
- Topic: Semiphore failure in v2.6.8
- Replies: 3
- Views: 3380
Re: Semiphore failure in v2.6.8
I neglected to say that the example program is running on a NANO54415 Dev Kit board. Plus I misspelled the example program name. It's DSPI2Serial.
Steve
Steve
- Mon Oct 20, 2014 11:02 am
- Forum: NetBurner Software
- Topic: Semiphore failure in v2.6.8
- Replies: 3
- Views: 3380
Semiphore failure in v2.6.8
In v2.6.7 the code below works. In v2.6.8 the OSSemPend() never returns. This is in example program DSPISerial.
DSPIStart(DEFAULT_DSPI_MODULE, TXBuffer,
RXBuffer, num, &DSPI_SEM); // Send data via DSPI
OSSemPend( &DSPI_SEM, 0 ); // Wait for DSPI to complete
Steve
DSPIStart(DEFAULT_DSPI_MODULE, TXBuffer,
RXBuffer, num, &DSPI_SEM); // Send data via DSPI
OSSemPend( &DSPI_SEM, 0 ); // Wait for DSPI to complete
Steve
- Mon Oct 20, 2014 10:58 am
- Forum: NetBurner Software
- Topic: Debug Build failure
- Replies: 31
- Views: 40320
Re: Debug Build failure
Using the serial port I loaded another example program that has always worked, LedBinaryCounter, and now the board is back alive. I'm bailing on the debug issue. It's clear to me no one really knows anything about debug, and I've wasted most of week trying to get a simple example program to run in ...
- Mon Oct 20, 2014 9:05 am
- Forum: NetBurner Software
- Topic: Debug Build failure
- Replies: 31
- Views: 40320
Re: Debug Build failure
A new development. After the debugger crashed as I explained in my previous post, the dev kit board has dropped off the network. I can't ping it. Eclipse can't find it. IPSetup can't find it. I've power-cycled the board, closed and restarted Eclispe, and nothing. And the link light is blinking away ...
- Mon Oct 20, 2014 8:42 am
- Forum: NetBurner Software
- Topic: Debug Build failure
- Replies: 31
- Views: 40320
Re: Debug Build failure
Rebuilding the system directories from the commandline and doing "make debug" followed by "make" solved the linker error I was getting. The SPISerial example program now compiles and runs for both the Release and Debug builds.
However, I am still unable to single-step in the Debug build. When I ...
However, I am still unable to single-step in the Debug build. When I ...
- Fri Oct 17, 2014 2:32 pm
- Forum: NetBurner Software
- Topic: Debug Build failure
- Replies: 31
- Views: 40320
Re: Debug Build failure
Yes, as I stated in my previous post. Removing it makes no difference.
Steve
Steve
- Fri Oct 17, 2014 2:13 pm
- Forum: NetBurner Software
- Topic: Debug Build failure
- Replies: 31
- Views: 40320
Re: Debug Build failure
I should have also added that, in my latest version of the example program SPISerial, I have commented out all code, including #define _DEBUG, and the #ifdef _DEBUG that wrapped InitializeNetworkGDB(). Made no difference. Or rather, it made it worse. With code in place the program would compile ...