|
Read-Only
Author gowree sankar kurmana
Posted 31-Dec-2009 09:31 GMT
Toolset ARM
|
 No Algorithm found for: 20000000H - 20000B2FH
gowree sankar kurmana
i am doing project on AT91SAM9260 controller, but when i am trying
to download executable file using JLINK it fails with:
No Algorithm found for: 20000000H - 20000B2FH
Here's the log output:
Build target 'Target 1'
compiling main.c...
compiling board_memories.c...
board_memories.c(109): warning: #61-D: integer operation result is
out of range
compiling board_lowlevel.c...
compiling pio.c...
assembling board_cstartup_keil.s...
compiling pmc.c...
compiling cp15.c...
assembling cp15_asm_keil.s...
linking...
Program Size: Code=2824 RO-data=40 RW-data=0 ZI-data=8192
User command #1: fromelf.exe --bin -o E:\myproject\myproject.bin
E:\myproject\myproject.axf
"myproject.axf" - 0 Error(s), 1 Warning(s).
Load "E:\\myproject\\myproject.AXF"
VTarget = 3.261V
Info: TotalIRLen = 4, IRPrint = 0x01
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D112112: ICache: 8kB (4*64*32), DCache: 8kB
(4*64*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
Info: RTCK reaction time is approx. 126ns
Info: Auto JTAG speed: Adaptive
Info: J-Link: ARM9 CP15 Settings changed: 50078 from 78, MMU Off,
ICache Off, DCache Off
Info: TotalIRLen = 4, IRPrint = 0x01
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D112112: ICache: 8kB (4*64*32), DCache: 8kB
(4*64*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
DLL version V4.08b, compiled Jun 30 2009 19:10:31
Firmware: J-Link ARM V8 compiled Jun 30 2009 11:00:16
Hardware: V8.00
Hardware-Breakpoints: 2
Software-Breakpoints: 2048
Watchpoints: 0
Found 1 JTAG device, Total IRLen = 4: Id of device #0: 0x0792603F
ARM9 identified.
Using adaptive clocking instead of fixed JTAG speed.
Info: TotalIRLen = 4, IRPrint = 0x01
Info: CP15.0.0: 0x41069265: ARM, Architecure 5TEJ
Info: CP15.0.1: 0x1D112112: ICache: 8kB (4*64*32), DCache: 8kB
(4*64*32)
Info: Cache type: Separate, Write-back, Format C (WT supported)
Using adaptive clocking instead of fixed JTAG speed.
No Algorithm found for: 20000000H - 20000B2FH
Erase skipped!
|
|
Read-Only
Author Chris Burrows
Posted 31-Dec-2009 10:04 GMT
Toolset ARM
|
 RE: No Algorithm found for: 20000000H - 20000B2FH
Chris Burrows
Google returns a few results for "keil no algorithm found for"
e.g.
http://www.keil.com/support/docs/2831.htm
If that doesn't help investigate some of the others.
|
|
Read-Only
Author Thorsten de Buhr
Posted 1-Jan-2010 14:05 GMT
Toolset ARM
|
 RE: No Algorithm found for: 20000000H - 20000B2FH
Thorsten de Buhr
> No Algorithm found for: 20000000H - 20000B2FH
Hi,
this nomally means that you forgot to select an algorithm in the
third tab of the target driver configuration dialog (utilities ->
select JLink driver -> 'Add' and select "your" flash algorithm
from the list.
That should work. If not, please report this problem to keil
support, and I'll solve it when I'm back next week.
BR,
/th.
|
|
Read-Only
Author gowree sankar kurmana
Posted 2-Jan-2010 03:55 GMT
Toolset ARM
|
 RE: No Algorithm found for: 20000000H - 20000B2FH
gowree sankar kurmana
hi,
i had tried to add algorithm in utilities -> select JLink
driver -> 'Add' and select "your" flash algorithm from the
list.but i didn't find any algorithm for AT91SAM9260 (SDRAM). can you
help me out to solve this problem
|
|
Read-Only
Author Andy Neil
Posted 2-Jan-2010 14:03 GMT
Toolset ARM
|
 RE: this nomally means that you forgot to select an algorithm
Andy Neil
I think it can also mean that your memory set-up is wrong?
As the message suggests, the Algorithm needs to be correct for
the specified address range - so, if the address range is wrong,
you can get this message.
|
|
Read-Only
Author Andy Neil
Posted 2-Jan-2010 14:10 GMT
Toolset ARM
|
 RE: this nomally means that you forgot to select an algorithm
Andy Neil
I have a feeling that the Algorithm could be one of those things
that uVision-3 stores in the "wrong" file; ie, it stores it in the
project.opt file, rather than the
project.uv2 file?
This means that, if you save/copy just the
project.uv2 file, you lose the Algorithm setting and,
therefore, you are likely to get this error the first time you try to
debug...
:-(
|