Target behaving differently under LPCXpresso and stand alone?

取消
显示结果 
显示  仅  | 搜索替代 
您的意思是: 

Target behaving differently under LPCXpresso and stand alone?

659 次查看
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JesperWe on Thu Jan 09 06:03:24 MST 2014
I have made a nice little sensor controller board running with a LPC11U36.
It runs perfectly when I start it using an LPCXpresso debug session (via LPC-Link).
But as soon as I disconnect the debugger and let it boot on its own it stops working.

I have a heartbeat led on the board so I know the task scheduler is running fine, and it sends result data on the uart as it should. But the data is all wrong, so it looks like the I2C bus interface is not working. But I can't find what's wrong because as soon as I connect the debugger it works perfectly.

Any ideas what could cause the MCU to behave differently when started by the debugger and when running free?

/j
0 项奖励
回复
2 回复数

645 次查看
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by JesperWe on Thu Jan 09 23:11:57 MST 2014
So... after a bit of head scratching I realized that the main difference is that the automatic breakpoint at the start of main() introduces a pause between the reset code and the start of the application, and that was the cause of the problem (without the debugger the boot was too fast for some sensors).

/j
0 项奖励
回复

645 次查看
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by R2D2 on Thu Jan 09 06:37:15 MST 2014
Are you using Semihosting (Lib)?
0 项奖励
回复