Memory Map ServoPod

[tichy]

All the Info is not consistent to me:
Memory Map for the 56807DSP says:
User Program Flash 1400-3FFF + 8000-EFFF thats 39934 dec words.
FPAVAIL says 9470. :confused:
Program RAM User F000-F7DF thats 2016 dec words.
PAVAIL says 2016. :)
EEAVAIL says 4096. not in memory map?
AVAIL says 3393, should be 3515 following memory map.
Can somebody elude me?
Thx

[nmitech]

Sorry, The memory map in the IsoMax document is not up to date for the latest released V0.82

Here is a way to find out the ServoPod user memory map for V0.82. This method can be used to check on any version start from V0.61 and latest.

IsoMax V0.82
OK
HEX OK

( program flash )
PFDP @ U. 5802 OK ( beginning of user program flash )

Since the PFAVAIL word is only used to calculate the contiguous memory for the compatibily with other smaller flash memory cpu such as IsoPod, TiniPod, PlugaPod, MiniPod. Therefore, it does not take the top 28K memory into account. So the correct program flash available should be,
PFAVAIL EFFF 8000 - + U. 94FD OK ( 38141 dec )
or create a new word,
: NEW-PFAVAIL 7D00 PFDP @ - EFFF 8000 - + ; OK
NEW-PFAVAIL U. 94FD OK ( 38141 dec )

( program ram )
PDP @ U. F000 OK ( user program ram begin)
or , PHERE U. F000 OK

F7E0 F000 - U. 7E0 OK ( available )

verify,
PAVAIL U. 7E0 OK

( data ram )
HERE U. 2BE OK ( user data ram begin )
or, DP @ U. 2BE OK

FFF 2BE - U. D41 OK ( available )

verify,
AVAIL U. D41 OK


( data flash )
Please see the related post for latest info on the EEAVAIL,
http://www.newmicros.com/discussion/showthread.php?t=1156&highlight=EEAVAIL

[tichy]

Thx, gaining more knowledge every day...
Forth is very unusual for an old C/C++ guy :eek: , but I hope to grasp it some day.
Trying to make friends with the stack right now, reverse thinking for me, but funny nevertheless. :)
Many thanks for your kind support in this forum!
The ServoPod is really a useful little powerboard. Two suggestions:
1) The LEDs are very useful, but add output pins for those in order to hook up a logic analyzer, I like my digiview very much for that purpose. Kind of a complete lab on my notebook!
2) Provide a jumper to supply Vin (6V, 3.7A from my switching supply) directly to V+ for the servos. Would be a comfartable solution also for feeding the board later on a robot with 4-5 cell NiMH.
Thx again, and have a nice time :)
Fried, an European livin' in Germany

[RMDumse]

Most people make the stack much harder than it has to be.

Here's a trick that might help.

Figure things on the stack as being arranged left to right, with the oldest thing on the left. Next what ever operation you're thinking about doing, just slide between the next to most right, and the most right. It will read as normal mid fix that way. So for example:

2 3 4 ( on stack )
+ ( operation )
* ( operation )

Here's how that translates with the above visualization

2 3 4 + becomes 2 3 + 4 so you add 3 + 4 and get a 7 result.

So your new stack looks like this

2 7 and you do your next operation * becomes 2 * 7 so you multiply the 2 times the 7.

Now lets say you are using variables, approach it the same way

A @ B @ C @

there they are on the stack. Contents of A is oldest, then B and then C is the newest, left to right. Now you want to add B and C contents and then multiply that by A contents, so the code is:

A @ B @ C @ + *

But you can visualize it as moving the operator between the two last things on the stack

B @ + C @ becomes a new result we'll call "D"

then move the next operator between the two things on the stack

A @ * "D"

Once I got the idea I could visualize this way, my problems with the stack went down to "almost none at all".

I hope this might help you too, but I realize everyone's brain works a little different.