Error "No source available for "us_ticker_read() at 0x7afa" on LPC1768

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Error "No source available for "us_ticker_read() at 0x7afa" on LPC1768

923件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by mbochud on Mon Oct 13 07:02:46 MST 2014
Hi Everybody,

I have my own board (with LPC1768) connected through the LPC-LINK2 board (jtag) to the LPCxpresso. The ISP pin (P2[10]) has is external pull-up.
My problem is when I start the debug mode I always have an error "- No source available for "us_ticker_read() at 0x7afa".
The error starts last week and before everything was working fine. I don't know what I change to have this error.
Is anybody knows what it can come from ? I'm looking for several days in forum, but I don't find anythings about it.

Thanks in advance and all the best,

Martin
ラベル(1)
0 件の賞賛
返信
3 返答(返信)

881件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Tue Oct 14 00:08:16 MST 2014
Where does us_ticker_read() come from within your code base. It isn't inside a prebuilt library with no debug information is it? If you aren't sure where it is, look inside the map file generated by the linker and see where it is pulled from.

Regards,
LPCXpresso Support
0 件の賞賛
返信

881件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by mbochud on Mon Oct 13 08:05:40 MST 2014
Hi,

I'm trying with a debug build (-g option).

here are all the compiler options :

-std=gnu++0x -D__NEWLIB__ -DTARGET_LPC176X -DTARGET_NXP -DTARGET_UBLOX_C027 -D__CORTEX_M3 -D__CODE_RED -DCPP_USE_HEAP -DTARGET_M3 -DTOOLCHAIN_GCC_CR -DTOOLCHAIN_GCC -DARM_MATH_CM3 -DMBED_BUILD_TIMESTAMP=1410198304.51 -D__MBED__=1 -DTARGET_LPC1768 -DTARGET_FF_ARDUINO -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\HTTPClient" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\HTTPClient\data" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\Waterclick" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\NTPClient" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\RTC" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed\TARGET_UBLOX_C027" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed\TARGET_UBLOX_C027\TOOLCHAIN_GCC_CR" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed\TARGET_UBLOX_C027\TARGET_NXP" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed\TARGET_UBLOX_C027\TARGET_NXP\TARGET_LPC176X" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\mbed\TARGET_UBLOX_C027\TARGET_NXP\TARGET_LPC176X\TARGET_UBLOX_C027" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\crc32" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\C027_Support" -I"D:\01_Geoazimut\LPC_Workspace\waterclick_1.0.0\C027_Support\Socket" -Og -g -Wall -c -fmessage-length=0 -fno-builtin -ffunction-sections -fdata-sections -fno-exceptions -mcpu=cortex-m3 -mthumb -D__NEWLIB__
0 件の賞賛
返信

881件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Mon Oct 13 07:10:51 MST 2014
Are you trying to debug with a "Release" build? Or did you remove the Debug symbol information from your build settings (-g option)
0 件の賞賛
返信