with and without jtag and ethernet

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

with and without jtag and ethernet

723 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by marionFR on Wed Jun 25 01:18:52 MST 2014
Hello,

On our board designed wih LPC 1833, ethernet works fine when i-jet is plugged and is running.
Without the i-jet, with exactly the same code, ethernet doesn't work at all.
Do you have any idea of where the problem could come from ?

Thanks

Marion
Labels (1)
0 Kudos
Reply
3 Replies

714 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Sep 08 07:30:48 MST 2015
LPCXpresso IDE does not  provide any default debugger init script for LPC1768, as no configuration is required.

The usual reason for application running when the debugger is connected, but not running when the debugger is not connected is that your application has been built to use semihosting operations:

[list]
  [*]https://www.lpcware.com/content/faq/lpcxpresso/semihosting
[/list]

If you need further assistance, I suggest that you create a new thread containing full details of your hardware and software setup, along with a full description of the problems that you are seeing.

Regards,
LPCXpresso Support
0 Kudos
Reply

714 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by rody on Tue Sep 08 05:50:23 MST 2015
I have the same problem with the LPC1768.

"the debugger runs an init script"
Where can I find this script?

I'm using lpcXpresso 7.8

Regards,
Rody.
0 Kudos
Reply

714 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by bavarian on Mon Jun 30 05:22:41 MST 2014
It's for sure not related to Ethernet as such, but to a setting which affects the Ethernet operation. For example

[list]
  [*]  setup of VTOR (pointer to interrupt vector table)
  [*]  setup of external memory for the Ethernet buffers
  [*]  clock tree settings
[/list]

When code works with debugger, but not without it,  most of the time it's because the debugger runs an init script which makes some required system settings. If they are missing in the code you will only notice it when the debugger script is not running.

Regards,
NXP Support Team
0 Kudos
Reply