SYGSYS:Bad System Call in __write()

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

SYGSYS:Bad System Call in __write()

987件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by djlegge on Fri Aug 23 03:00:00 MST 2013
Hi I am using LPCXpresso 5.2.6 in linux (Ubuntu 12.04) and have found what I think to be a small bug (or limitation) in the semihosting support.

I am debugging application code which is (in debug configuration) approx 110kB in size (the 'text' segment given by arm-none-eabi-size).

I have a secondary boot loader, so my application code is loaded in to memory at 0x8000.

I am using the semihosting printf() feature and it works well until __write() moves above 0x20000. At this point, the printf output is still shown but the debugging stops with the above error.

I am using the free (128kB limited) version of LPCXpresso. I suspect somehow this is to do with the 128kB debug limit for this licence ?

Any ideas ? Thanks. 
0 件の賞賛
返信
2 返答(返信)

977件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by djlegge on Fri Aug 23 03:30:06 MST 2013
Thanks for the quick reply.
I had assumed the 128k limit was an actual code size limit, rather than to do with the 0x20000 boundary - especially as it gives no errors programming.
For now I'll remove my bootloader for debugging purposes.
Thanks.
0 件の賞賛
返信

977件の閲覧回数
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by lpcxpresso-support on Fri Aug 23 03:05:32 MST 2013
That is correct, this is caused by the 128k debug limit.
0 件の賞賛
返信