Mike,
Something is really messed. probably beginning with the hex
utility. It looks like maybe the "ROM width geometry" and your "ROM width"
[8] are different.
TIP:
To look at your actual FLASH code, use the handy addition to the 6711 DSK
GEL file below. A problem that commonly occurs is that you need to
configure the memory for "32 bit mode" to access the LEDS/Switches, etc. but you
need to configure it in "8 bit mode" to properly access the flash.
In 8 bit mode you should be able to view or disas mem at 0x90000000 to see
your code.
mikedunn
menuitem "Set_CE1";
hotmenu Set_CE1_8bit() { CE1_8bit; }
hotmenu Set_CE1_32bit() { CE1_32bit; }
Mike Petty
<m...@nmt.edu> wrote:
This is kind of an update to the problem I was having
before.
I think that my problem has something to do with either the
copy from the first 1K of flash to memory upon bootup or with the hex file
translation. If I burn my program into flash, say a section of it looks
like this (when I use the view flash contents option in flashburn): 00 29 AA 33
After burning, I reset the DSP and go into code composer,
where I look at memory address 0x00000000. It's contents would look
something like this:
0xFFFF0000 0xFFFF2929 0xFFFFAAAA 0xFFFF3333
Is that what is should look like? I can see how the
translation is happening, but when I look at my assembly source in mixed
mode, it doesn't seem to make much sense.
I'm not
sure that I even trust Code Composer to tell me what's right. For
example, if I load the symbols, then it
says the PC points to my first instruction, but then when it executes
something like mvkl 0x05,B4 I watch the B4 register and it doesn't
change. So, it's not even executing that instruction, but code
composer shows that it is. This only happens on programs that are burnt to
flash. Everything works on programs that aren't.
MikeMike
Petty wrote:
>I've been working with some boot code that I
wrote and it's been working >beautifully for months. I basically
just opened up the gel file to get >the needed EMIF values and
addresses, then initialized that and did my >copying. > >But now I'm having a problem, and I have no idea why. What I did was
>add some HWI's. Then I got a warning that my stack size was too
small. >I naively ran it once just to see what would happen. It
didn't work, so >I increased the stack size. But it still
didn't boot. Played around >with it some, but it still
didn't work. So I went back to my old code >and programmed that
into the flash, and that didn't boot either. I'm >pretty
positive that the same code was working a couple weeks before. > >So, then I started stepping through the code. While I'm initializing
>the EMIF interface, I go to do a stw to one of the registers and the
DSP >jumps (maybe resets? But I don't think so) to a point earlier
in the >boot code. So effectively, whenever I store this value it just
jumps me >to a previous spot in the code. It's just a standard
EMIF register that >I'm writing this to. I've tried stepping
over the bad portion. >Sometimes CCS crashes (telling me that it's
possibly corrupted memory or >a stack overflow), other times it lets
me, but since I skipped a step, >the EMIF doesn't initialize and
everything is worthless. > >I've ran all the diagnostics
included, and everything checks out. > >So,
my question is does anyone know of any peculiarities that smashing a >stack might have that would cause this behavior? Does anyone know of >anything that would cause this behavior? I thought I had seen this >problem before when I had some grounding issues, but I'm pretty sure
>that's not the case now. Is there some setting I could have
corrupted >that a power-cycle would not get rid of? I haven't seen
anything that >jumps out at me. > >Lastly, is there
some way to put the DSP into the factory default >settings or anything?
Possibly a way to just start anew? Any help >would be appreciated,
I'm pulling my hair out over this one. > >Oh, and I'm
on a c6713 DSK. > >Mike
Petty>_____________________________________ >Note: If you do a simple
"reply" with your email client, only the author of this message will receive
your answer. You need to do a "reply all" if you want
your answer to be distributed to the entire group. > >_____________________________________ >About this discussion
group: > >To Join: Send an email to c...@yahoogroups.com > >To Post: Send an email to c...@yahoogroups.com > >To Leave: Send an email to c...@yahoogroups.com > >Archives: http://www.yahoogroups.com/group/c6x > >Other
Groups: http://www.dsprelated.com > >Yahoo! Groups Links
_____________________________________ Note: If you do a simple
"reply" with your email client, only the author of this message will receive
your answer. You need to do a "reply all" if you want your answer to be
distributed to the entire group.
_____________________________________ About this discussion group:
To Join: Send an email to c...@yahoogroups.com
To Post: Send
an email to
c...@yahoogroups.com
To Leave: Send an email to
c...@yahoogroups.com
Archives:
http://www.yahoogroups.com/group/c6x
Other Groups:
http://www.dsprelated.com
Yahoo! Groups Links
<*> To
visit your group on the web, go to: http://groups.yahoo.com/group/c6x/
<*> To unsubscribe from this group, send an email to: c...@yahoogroups.com
<*>
|