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?
@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
USB_BASE EQU 0x40050000 USB0_CSRL0 EQU 0x102 LDR R1,=USB_BASE LDRB R0,[R1,#USB0_CSRL0] ; No error !!!!
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.
I know the differences of .N and .W suffix. Limits of the immediate offset of the cortex m3 LDR command can not be between the 0x00 and 0x1F. Therefore assembler gives wrong error.
You don't know that. You have no idea what's important for your main question and what isn't.
Else you cant see and you cant understand the niceties in my questions.
There are no "niceties" to be found in any of the pointless repetitions of your question. Just the obnoxiousness of a person who asks a question, then is so sure he knows the answer better than the people he asked, that he considers himself qualified to dismiss answers as unhelpful without so much as pretending to consider them first.
You don't want any help, fine --- so stop wasting everybody's time by pretending to ask for it.
I found the answer for my first question and i wrote it. This is an assembler's problem and i think at the next versions Keil repairs.
If you look at the answers to my question unrelated ordinary conceivable that you will see the answers.
I'm not coming here to chat or controversy. I'm coming to find a single reply of my question I was just right.
At the same time the problem is only missing my Ingilizce Caused by.
I found the answer for my first question and i wrote it.
So you believe. Just about everybody, up to and including the company that designed both the CPU and the assembler you're using, disagrees with you on that count.
I'm coming to find a single reply of my question I was just right.
Well, this is a discussion forum, not a "I believe you" automaton. We're people, not Electric Monks (courtesy Douglas Adams).
In other words: if you can't stand the heat, stay out of the kitchen.
This place is technical forum. You're not going to social sciences forums, why?
(Let wait the new version of assembler compilers)
Go away, please. Enough is enough!
Did you see anything about "Some or all forms of this instruction are 16-bit (narrow) instructions in Thumb-2 code. For details see [...]"?