Bug in 5.0.14 arm-none-eabi-as.exe

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

Bug in 5.0.14 arm-none-eabi-as.exe

237 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MikeSimmonds on Mon Feb 04 12:54:01 MST 2013
[FONT=Tahoma][SIZE=1]The assembler supplied with LPCXpresso 5.0.14 generates the wrong opcode.
Sample project attached.
I asked for orrs r0, (1<<27), but got orrs r0, -1
When you fix this, [I]please[/I] check other opcodes that use the same
immediate encoding in the instructions they generate.
[/SIZE][/FONT][FONT=Tahoma][SIZE=1]
**PLEASE CHANGE THE TOOLS PATH IN THE MAKEFILE FOR YOUR PC **
[/SIZE][/FONT][FONT=Tahoma][SIZE=1]
Background to the sample:
I can't use 5.0.14 as the debugger crashes (a fix is promised for the next release:))
so I have to stay with 4.3.0 in the mean time

I copy the 5/14 tools (to a separate directory) under my 4.3 installation
and my makefiles target this.

With 4.3, the IDE, apparently,  does not know how to to find its own make.exe
(in <install>/msys/bin)!
Not even when I add the specific path via Windows/Preferences/LPCXpresso/Paths and Directories.
So in the project properties I have to tell it not to use the default build command,
but give the explicit path to 'make'. Remember to change this path to suit
your own PC.

Normally, of course, I would run make from a DOS box up until I need to debug;
but I don't expect you to do that.

Regards, Mike

[/SIZE][/FONT]
0 Kudos
2 Replies

228 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by MikeSimmonds on Mon Feb 04 18:24:37 MST 2013
[FONT=Trebuchet MS][SIZE=1]It the user (me!) again, not the assembler. Sorry
I would delete the thread if I could, but looks
like its staying for all to see my ineptitude.

[/SIZE][/FONT][FONT=Trebuchet MS][SIZE=1]
Quote: cfb
I can see (1<27) in your code not (1<<27).


Thanks. I just noticed it for myself -- should have checked back [I]hours[/I] ago.

I spent over 4 hours debugging to find where I [I]thought[/I] the assember[/SIZE][/FONT][FONT=Trebuchet MS][SIZE=1] had
failed me. And now I see that it's my fault. I don't post without thinking
-- how many times must I have looked at my source without recognising
the typo -- and of course, "(1<27)" is legal i.e true, i.e minus one.


[/SIZE][/FONT]
0 Kudos

228 Views
lpcware
NXP Employee
NXP Employee
Content originally posted in LPCWare by cfb on Mon Feb 04 13:40:05 MST 2013

Quote: MikeSimmonds

[FONT=Tahoma]I asked for orrs r0, (1<<27), but got orrs r0, -1[/FONT]


I can see (1<27) in your code not (1<<27).
0 Kudos