Compiler give error message for following codes. A1174E: "Data transfer offset 0x00000102 out of range. Permitted values are 0x00..0x1F"
LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; Error code is A1174E !!!! USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102
But compiler dont give any error if i write this program thats way
USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102 LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; Error code is A1174E !!!!
What is wrong?
Andy is (once again) absolutely correct - Why do you not take note of the responses you receive?
"What is wrong?"
As the assembler reports, the offset is out of range. It is even helpful enough to tell you what the acceptable range is.
So ... The reason the assembler is rejecting your code is because it is invalid.
As I said before, you really should read up on the fundamentals of the ARM core.
"As I said before, you really should read up on the fundamentals of the ARM core."
And not hurtful to also check out the differences between classical ARM instructions, and Thumb or Thumb-2 instructions.
It comes down to this - the OP, just like so many of his kind that land here, does not want to work hard. He wants somebody to give him a one-liner, no-brainer solution to solve his problem. There will be more of them.
... and writing in Assembly is, by definition, hard work.
It remains a mystery why he insists on struggling with assembly; he clearly isn't going to outsmart a compiler any time soon - so why not just use 'C' ?!
My first message wrong written.
Compiler give error message for following codes.
A1174E: "Data transfer offset 0x00000102 out of range. Permitted values are 0x00..0x1F" LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; Error code is A1174E !!!! USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102
USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102 LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; No error !!!!
What is wrong in first one which gives error?
----------------------------------------
Could you please answer my question, and discuss yours anywhere else.
Why? You're not listening to anything that anyone tells you anyhow.
You still don't understand the difference between an Assembler and a Compiler. Understanding & paying attention to subtle distinctions like that is absolutely fundamental if you want to be an Assembly programmer.
If you consider such details too trivial for you to bother with, then Assembly programming is not for you.
www.milinkito.com/.../bart.php
@Andrew
Assembler and/or compiler not importand details for my main question.
Please focus on the main question. Else you cant see and you cant understand the niceties in my questions. Because your brain looking other destinations.
You little tyrant!
You_little_tyrant equ 1 MOV R0,#You_little_tyrant ; No error !!!!
MOV R0,#You_little_tyrant ; No error !!!! You_little_tyrant equ 1
But folowing program produce the error code A1174E !!!!
LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; Error code is A1174E !!!!
USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102
I think Keil assembler has a bug.
Because folowing error meaningless for the LDR assembly command.
A1174E: "Data transfer offset 0x00000102 out of range. Permitted values are 0x00..0x1F"
Isnt it Tamir ?
Sory;
Because folowing error meaningless for the LDRB assembly command.
If the offset is limited to 0x00 to 0x1f does depend on a couple of things, doesn't it?
For example what chip you have, or what mode you are assembling (not compiling) for. Have you maybe seen the limit 0 to 31 somewhere in any instruction set descriptions?
By the way - when you did decide that the assembler had a bug - did you check what the produced op code result was from your source code?
Are you going to read the assembler manual anytime soon or what?!
So sorry i forget to said "I use cortex m3 family".
Find out and think about the differences between these two instructions below and what a two pass assembler is faced with in the two situations above.
LDRB.N R0,[R1,#USB0_CSRL0] LDRB.W R0,[R1,#USB0_CSRL0]
@Per Westermark
My processor is CM3. Limits of Immediate ofset mode of the LDR command are -255 to 4095.
Therefore i think Keil assembler gives a wrong error message.