-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unexpected error Branch out of range (-64 <= k <= 63) #47
Comments
List file: |
Mminor remark, i hope this will be helpful. No cheking garbage in second operand - mnemonics.c line429. Strange checking relative addres for branch mnemonics.c line437. |
This issue is no longer actual for me. Thank you very much, AVRA sources is very helpful.avra -I /home/kostas/repos/w5277c/core5277/ "main.asm" -m "main.asm".map -l "main.asm".lst (в каталоге: /home/kostas/repos/w5277c/5277.ru/firmware/solid_relay_x4_v1.0) -And---------------------------------------------------------------------------------- JAVRA Java AVR macro assembler Version 0.0.1 WARNING! The project is not finished yet, it is under development. Warning[1] ./devices/atmega168.inc(18): unsupported #pragma Total : 6196 words (12392 bytes) Build SUCCESS, warnings:6 |
Sorry I was of no help, but I'm glad this isn't a problem for you any more. And thanks for pointing out some bugs in mnemonics.c, although I don't have time to look into it them right now. IMO, most of mnenomics.c is a mess and should be rewritten. |
Hi,
In projects with a lot of labels, I get an unexpected error:
core5277/./core/ram/_ram_find_used_block_mt.inc(42) : Error : Branch out of range (-64 <= k <= 63)
In code:
LDI LOOP_CNTR,0x00
LDI ZH,high( _C5_DRIVERS_HEADER)
LDI ZL,low( _C5_DRIVERS_HEADER)
_C5_RAM_FIND_USED_BLOCK_MT__LOOP1:
CALL _C5_RAM_FIND_USED_BLOCK_MT__BODY
ADIW ZL,_C5_DRIVER_HEADER_SIZE
INC LOOP_CNTR
CPI LOOP_CNTR,C5_DRIVERS_QNT
;42 line:
BRNE _C5_RAM_FIND_USED_BLOCK_MT__LOOP1
In other projects, the error appears in other places, but is always associated with labels and branches.
Reproducible on current version as well as on 1.3.0
Best regards,
Konstantin.
The text was updated successfully, but these errors were encountered: