Posted by Vien Nguyen Another dumb question here. Everyone knows that these flash chips could be erased/rewritten officially 100 times (practically maybe more). This is not a problem w/ production, but it's is a problem w/ debugging. By looking at the map file generated by the linker, when you link your appl. with the HMON for debugging, even though your appl. resides in RAM, but the HMON is still mapped to the on-chip Flash. Thus, it seems to me that everytime I run the debbuger, the chip will get erased and reflashed because of the HMON. Am I correct? I hope I am wrong here. Could someone shed some light here? How do you debug your appl? w/ or w/o using HMON? how do you configure or set up your debbuging session so that the on-chip flash is not touched everytime the debugger is launched? One more thing, it's about shawdow vectors. I've heard about that, and know that I have to use it in order to debug my appl in RAM, but I am not quite sure how to do it. Could someone please explain how to this, or give some guideline? Thank you all in advance, and I really appreciate your great help. Best regards, Vien Nguyen. --------------------------------------- Below is the map file generated by Hitachi toolchains. I use HEW2.1 -------------------------------------- Hitachi Optimizing Linkage Editor (Ver. 7.1.05.003)24-Apr-2003 21:10:40 *** Options *** -subcommand=D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\EDK2329.hlk *** Error information *** *** Mapping List *** SECTION START END SIZE ALIGN RESET_VECTOR
![]()
on April 25, 2003, 17:53:35
64.114.124.58
Hi all,
I am new here, so please bear with me.
I just bought a EDK2329 kit. Following the tutorial, I could repeat the tutorial quite well, except one small glitch. Once I have the kernel flashed on the chip in Boot mode successfully, sometimes I could not run the same tutorial in User mode, as instructed in the tutorial. If I switch the jumper CJ4-B as instructed, the debugger could not connect to the board at all. Could someone explain?
EDK2329 memory map is as follow:
0x00000 - 0x60000 : 384K of on-chip FLASH
0x80000 - 0xBFFFF : 256k x 16 external RAM
0xFF7C00 - 0xFFFBFF: 32K on-chip RAM
binary "D:\Program Files\HEW21\EDK2329\EDK2329\uGenU.cde"(FDTUserModeMicroKernel,FDTUserModeMicroKernel)
binary "D:\Program Files\HEW21\EDK2329\EDK2329\FDTInit.cde"(FDTInit,FDTInit)
noprelink
rom D=R
nomessage
list "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\EDK2329.map"
nooptimize
start FDTInit/01000,CUser_Vectors/02000,PHMON,CHMON/05000,FDTUserModeMicroKernel/0F600,PResetPRG,PIntPRG/080000,C$DSEC,C$BSEC,P,D/080400,B,R/0FFE000,BHMON/0FFF700,S/0FFFA00
nologo
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\dbsct.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\hmonconfiguser.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\hmonserialconfiguser.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\hwsetup.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\intprg.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\main.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\resetprg.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\sbrk.obj"
input "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\vectors.obj"
library "D:\Program Files\HEW21\EDK2329\EDK2329\EDK2329_HMON.lib"
library "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\EDK2329.lib"
output "D:\Program Files\HEW21\EDK2329\EDK2329\debug_with_hmon\EDK2329.abs"
end
00000000 00000003 4 0
$VECT5
00000014 00000017 4 2
$VECT7
0000001c 0000001f 4 2
TRAP_VECTORS
00000020 0000002f 10 0
$VECT16
00000040 00000043 4 2
$VECT17
00000044 00000047 4 2
$VECT18
00000048 0000004b 4 2
$VECT19
0000004c 0000004f 4 2
$VECT20
00000050 00000053 4 2
$VECT21
00000054 00000057 4 2
$VECT22
00000058 0000005b 4 2
$VECT23
0000005c 0000005f 4 2
$VECT24
00000060 00000063 4 2
$VECT25
00000064 00000067 4 2
$VECT26
00000068 0000006b 4 2
$VECT28
00000070 00000073 4 2
$VECT32
00000080 00000083 4 2
$VECT33
00000084 00000087 4 2
$VECT34
00000088 0000008b 4 2
$VECT35
0000008c 0000008f 4 2
$VECT36
00000090 00000093 4 2
$VECT40
000000a0 000000a3 4 2
$VECT41
000000a4 000000a7 4 2
$VECT42
000000a8 000000ab 4 2
$VECT43
000000ac 000000af 4 2
$VECT44
000000b0 000000b3 4 2
$VECT45
000000b4 000000b7 4 2
$VECT46
000000b8 000000bb 4 2
$VECT47
000000bc 000000bf 4 2
$VECT48
000000c0 000000c3 4 2
$VECT49
000000c4 000000c7 4 2
$VECT50
000000c8 000000cb 4 2
$VECT51
000000cc 000000cf 4 2
$VECT52
000000d0 000000d3 4 2
$VECT56
000000e0 000000e3 4 2
$VECT57
000000e4 000000e7 4 2
$VECT58
000000e8 000000eb 4 2
$VECT59
000000ec 000000ef 4 2
$VECT60
000000f0 000000f3 4 2
$VECT61
000000f4 000000f7 4 2
$VECT62
000000f8 000000fb 4 2
$VECT63
000000fc 000000ff 4 2
$VECT64
00000100 00000103 4 2
$VECT65
00000104 00000107 4 2
$VECT66
00000108 0000010b 4 2
$VECT68
00000110 00000113 4 2
$VECT69
00000114 00000117 4 2
$VECT70
00000118 0000011b 4 2
$VECT72
00000120 00000123 4 2
$VECT73
00000124 00000127 4 2
$VECT74
00000128 0000012b 4 2
$VECT75
0000012c 0000012f 4 2
$VECT80
00000140 00000143 4 2
$VECT81
00000144 00000147 4 2
$VECT82
00000148 0000014b 4 2
$VECT83
0000014c 0000014f 4 2
SCI_VECTORS
00000150 0000015b c 0
$VECT88
00000160 00000163 4 2
$VECT89
00000164 00000167 4 2
$VECT90
00000168 0000016b 4 2
$VECT91
0000016c 0000016f 4 2
FDTInit
00001000 0000111d 11e 0
CUser_Vectors
00002000 00002003 4 2
PHMON
00005000 000072d9 22da 2
CHMON
000072da 00007421 148 2
FDTUserModeMicroKernel
0000f600 0000fe46 847 0
PResetPRG
00080000 0008000f 10 2
PIntPRG
00080010 00080081 72 2
C$DSEC
00080400 0008040b c 2
C$BSEC
0008040c 00080413 8 2
P
00080414 00080591 17e 2
D
00080592 000805a3 12 2
B
00ffe000 00ffe41f 420 2
R
00ffe420 00ffe431 12 2
BHMON
00fff700 00fff90f 210 2
S
00fffa00 00fffbff 200 2
Message Thread
![]()
« Back to index
Evaluation Kit Support
Renesas Evaluation Boards are intended for evaluation of Renesas microprocessors only, not as development tools.