SV: [basicstamps] Nothing on Memory Map Window?
Archiver
Posts: 46,084
Greetings!
Fra: Bruce Bates [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=Q7TisPnbcIELZ-JGSB9rNoNfZlXfmA7pgDEa00uEdfIfIhzWsSDoSOFAhfAKh4ZXDcYSQ3RzoVGclwFz]bvbates@u...[/url
> Additionally, as a side note, program memory starts at the bottom and
works it
> way up to the top of memory. Data memory starts at the top and works
its way
> down to the bottom. If you imagine a case where data memory could be
written
> and have the program memory corrupted by it, that is indeed the case.
Care
> is therefore recommended when writing to data memory.
That depends on your definition of 'top' and 'bottom' of memory...
Programs are stored from the highest address possible and towards 0.
That aside, if you know how much space your data will use you could
reserve it with the DATA statement.
(highly recommended)
:-)
Trygve
Fra: Bruce Bates [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=Q7TisPnbcIELZ-JGSB9rNoNfZlXfmA7pgDEa00uEdfIfIhzWsSDoSOFAhfAKh4ZXDcYSQ3RzoVGclwFz]bvbates@u...[/url
> Additionally, as a side note, program memory starts at the bottom and
works it
> way up to the top of memory. Data memory starts at the top and works
its way
> down to the bottom. If you imagine a case where data memory could be
written
> and have the program memory corrupted by it, that is indeed the case.
Care
> is therefore recommended when writing to data memory.
That depends on your definition of 'top' and 'bottom' of memory...
Programs are stored from the highest address possible and towards 0.
That aside, if you know how much space your data will use you could
reserve it with the DATA statement.
(highly recommended)
:-)
Trygve
Comments
>Greetings!
>
>Fra: Bruce Bates [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=S2CFvO5ewzdJjzW_31c4tGFCJWxuRwMhWZ9pkS-aG-KEZc3Ii5Wte4NQzzHeWWYzZpsHZTHF3JDkJnIXMjRYwYo]bvbates@u...[/url
>
> > Additionally, as a side note, program memory starts at the bottom and
>works it
> > way up to the top of memory. Data memory starts at the top and works
>its way
> > down to the bottom. If you imagine a case where data memory could be
>written
> > and have the program memory corrupted by it, that is indeed the case.
>Care
> > is therefore recommended when writing to data memory.
>
>That depends on your definition of 'top' and 'bottom' of memory...
>Programs are stored from the highest address possible and towards 0.
The topic was the Memory Map where Top and Bottom are fairly well defined,
visually. Your additional information is correct for those understand the
basics, and is certainly appreciated.
>That aside, if you know how much space your data will use you could
>reserve it with the DATA statement.
>(highly recommended)
The DATA statement still does not limit storage. Program/Data collisions can
still occur if the programmer is not careful about where they write data.
>:-)
>Trygve
Bruce Bates
data are stored. In the Memory Map Window it shows in red my program
starts from location $7FF downward. But I don't see a trace of my
data. If I used the @DATA reserve directive I could see clearly the
area I specified in green but with all "0"s in it. If I specify 64
bytes then the 64 bytes location will be coloured green. Is this
because of the security feature so others can peek the content of your
memory?
- Johari
--- In basicstamps@yahoogroups.com, "Trygve Henriksen"
<trygve.henriksen@v...> wrote:
> Greetings!
>
> Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
>
> > Additionally, as a side note, program memory starts at the bottom and
> works it
> > way up to the top of memory. Data memory starts at the top and works
> its way
> > down to the bottom. If you imagine a case where data memory could be
> written
> > and have the program memory corrupted by it, that is indeed the case.
> Care
> > is therefore recommended when writing to data memory.
>
> That depends on your definition of 'top' and 'bottom' of memory...
> Programs are stored from the highest address possible and towards 0.
>
> That aside, if you know how much space your data will use you could
> reserve it with the DATA statement.
> (highly recommended)
>
> :-)
> Trygve
or reserved. Why don't you post your DATA statements so we can have a
look.
-- Jon Williams
-- Parallax
Original Message
From: Johari Aziz [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=ozt5iS9kzUYvCBTzqwXpAF-LelRE2Z8uB6LWUYnqJQs7ar1uszy3yc0_9GlJvHJ18NQtnZPyNov0g_4m]johaziz@y...[/url
Sent: Thursday, August 21, 2003 12:28 PM
To: basicstamps@yahoogroups.com
Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
Yeah I understand the area where my program are stored and where my data
are stored. In the Memory Map Window it shows in red my program starts
from location $7FF downward. But I don't see a trace of my data. If I
used the @DATA reserve directive I could see clearly the area I
specified in green but with all "0"s in it. If I specify 64 bytes then
the 64 bytes location will be coloured green. Is this because of the
security feature so others can peek the content of your memory?
- Johari
--- In basicstamps@yahoogroups.com, "Trygve Henriksen"
<trygve.henriksen@v...> wrote:
> Greetings!
>
> Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
>
> > Additionally, as a side note, program memory starts at the bottom
> > and
> works it
> > way up to the top of memory. Data memory starts at the top and works
> its way
> > down to the bottom. If you imagine a case where data memory could be
> written
> > and have the program memory corrupted by it, that is indeed the
> > case.
> Care
> > is therefore recommended when writing to data memory.
>
> That depends on your definition of 'top' and 'bottom' of memory...
> Programs are stored from the highest address possible and towards 0.
>
> That aside, if you know how much space your data will use you could
> reserve it with the DATA statement. (highly recommended)
>
> :-)
> Trygve
To UNSUBSCRIBE, just send mail to:
basicstamps-unsubscribe@yahoogroups.com
from the same email address that you subscribed. Text in the Subject
and Body of the message will be ignored.
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
This message has been scanned by WebShield. Please report SPAM to
abuse@p....
' shows on memory map light green
' check ascii box to see it as string
' it goes to stamp when you F9 program.
DATA @16, 255(16) ' reserve 16 bytes starting at loc 16
' fill the 16 bytes with ff
' shows ff in light green on the memory map
' this is "defined data" and is put into the
' stamp eeprom when you F9 the program
DATA @48, (32) ' reserves 32 byte starting at 48
' shows dark green as 0 on the memory map
' this is "undefined data" and
' leaves contents of stamp memory unaffected
' whatever is in the stamp, is still there
' in those bytes after you F9 the program
' Note that memory is reserved in blocks of 16 bytes.
for i=0 to 15
write i+16,i ' puts i into location 16,..,31 at **run time**
next ' this does not show on the memory map.
write 2047,$ff ' overwrites program, crashes stamp at next reset
' does not show on memory map
' does not cause compiler error
>Yeah I understand the area where my program are stored and where my
>data are stored. In the Memory Map Window it shows in red my program
>starts from location $7FF downward. But I don't see a trace of my
>data. If I used the @DATA reserve directive I could see clearly the
>area I specified in green but with all "0"s in it. If I specify 64
>bytes then the 64 bytes location will be coloured green. Is this
>because of the security feature so others can peek the content of your
>memory?
>
>- Johari
>
>--- In basicstamps@yahoogroups.com, "Trygve Henriksen"
><trygve.henriksen@v...> wrote:
>> Greetings!
>>
>> Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
>>
>> > Additionally, as a side note, program memory starts at the bottom and
>> works it
>> > way up to the top of memory. Data memory starts at the top and works
>> its way
>> > down to the bottom. If you imagine a case where data memory could be
>> written
>> > and have the program memory corrupted by it, that is indeed the case.
>> Care
>> > is therefore recommended when writing to data memory.
>>
>> That depends on your definition of 'top' and 'bottom' of memory...
>> Programs are stored from the highest address possible and towards 0.
>>
>> That aside, if you know how much space your data will use you could
>> reserve it with the DATA statement.
>> (highly recommended)
>>
>> :-)
>> Trygve
>
>
>To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
>from the same email address that you subscribed. Text in the
>Subject and Body of the message will be ignored.
>
>
>Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
@DATA just to check that area of map inititially for testing. As I had
told I had to write another program of READ statements just to check
the data. That means the Memory Map window utility is just useless to
me. My data is there but I can't see it grapically.
- Johari
--- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...> wrote:
> You should only see zeros in your data area if that's what you specified
> or reserved. Why don't you post your DATA statements so we can have a
> look.
>
> -- Jon Williams
> -- Parallax
>
>
>
Original Message
> From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> Sent: Thursday, August 21, 2003 12:28 PM
> To: basicstamps@yahoogroups.com
> Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
>
>
> Yeah I understand the area where my program are stored and where my data
> are stored. In the Memory Map Window it shows in red my program starts
> from location $7FF downward. But I don't see a trace of my data. If I
> used the @DATA reserve directive I could see clearly the area I
> specified in green but with all "0"s in it. If I specify 64 bytes then
> the 64 bytes location will be coloured green. Is this because of the
> security feature so others can peek the content of your memory?
>
> - Johari
>
> --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> <trygve.henriksen@v...> wrote:
> > Greetings!
> >
> > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> >
> > > Additionally, as a side note, program memory starts at the bottom
> > > and
> > works it
> > > way up to the top of memory. Data memory starts at the top and works
> > its way
> > > down to the bottom. If you imagine a case where data memory could be
> > written
> > > and have the program memory corrupted by it, that is indeed the
> > > case.
> > Care
> > > is therefore recommended when writing to data memory.
> >
> > That depends on your definition of 'top' and 'bottom' of memory...
> > Programs are stored from the highest address possible and towards 0.
> >
> > That aside, if you know how much space your data will use you could
> > reserve it with the DATA statement. (highly recommended)
> >
> > :-)
> > Trygve
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject
> and Body of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> This message has been scanned by WebShield. Please report SPAM to
> abuse@p...
downloaded into the Stamp, NOT what your program will do to it later.
-- Jon Williams
-- Applications Engineer, Parallax
-- Dallas Office
Original Message
From: Johari Aziz [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=BzDgGdNH_yTqEyNKQ-svJRtqf9XkpjBvVHnpa01AHu0bN5TS54Ph60303AkNRgv118JsP01ps_-bULgJ]johaziz@y...[/url
Sent: Thursday, August 21, 2003 10:56 PM
To: basicstamps@yahoogroups.com
Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
It wasn't a DATA statement. It was WRITE statements. I just used the
@DATA just to check that area of map inititially for testing. As I had
told I had to write another program of READ statements just to check the
data. That means the Memory Map window utility is just useless to me. My
data is there but I can't see it grapically.
- Johari
--- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
wrote:
> You should only see zeros in your data area if that's what you
> specified or reserved. Why don't you post your DATA statements so we
> can have a look.
>
> -- Jon Williams
> -- Parallax
>
>
>
Original Message
> From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> Sent: Thursday, August 21, 2003 12:28 PM
> To: basicstamps@yahoogroups.com
> Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
>
>
> Yeah I understand the area where my program are stored and where my
> data are stored. In the Memory Map Window it shows in red my program
> starts from location $7FF downward. But I don't see a trace of my
> data. If I used the @DATA reserve directive I could see clearly the
> area I specified in green but with all "0"s in it. If I specify 64
> bytes then the 64 bytes location will be coloured green. Is this
> because of the security feature so others can peek the content of your
> memory?
>
> - Johari
>
> --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> <trygve.henriksen@v...> wrote:
> > Greetings!
> >
> > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> >
> > > Additionally, as a side note, program memory starts at the bottom
> > > and
> > works it
> > > way up to the top of memory. Data memory starts at the top and
> > > works
> > its way
> > > down to the bottom. If you imagine a case where data memory could
> > > be
> > written
> > > and have the program memory corrupted by it, that is indeed the
> > > case.
> > Care
> > > is therefore recommended when writing to data memory.
> >
> > That depends on your definition of 'top' and 'bottom' of memory...
> > Programs are stored from the highest address possible and towards 0.
> >
> > That aside, if you know how much space your data will use you could
> > reserve it with the DATA statement. (highly recommended)
> >
> > :-)
> > Trygve
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject
> and Body of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> This message has been scanned by WebShield. Please report SPAM to
> abuse@p...
To UNSUBSCRIBE, just send mail to:
basicstamps-unsubscribe@yahoogroups.com
from the same email address that you subscribed. Text in the Subject
and Body of the message will be ignored.
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
This message has been scanned by WebShield. Please report SPAM to
abuse@p....
PRESENT status, every single byte in every address just as other
Memory Map program back in DOS world. I'm sure people who have work
with other microcontrollers in DOS would agree. Even back during my
Apple II time I could monitor every location of my memory. That was
back in 1980. I think this is the year 2003. Come on you guys at
Parallax show me some real progress.
- Johari
--- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...> wrote:
> Remember that the Memory Map function is to show you what will be
> downloaded into the Stamp, NOT what your program will do to it later.
>
> -- Jon Williams
> -- Applications Engineer, Parallax
> -- Dallas Office
>
>
>
Original Message
> From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> Sent: Thursday, August 21, 2003 10:56 PM
> To: basicstamps@yahoogroups.com
> Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
>
>
> It wasn't a DATA statement. It was WRITE statements. I just used the
> @DATA just to check that area of map inititially for testing. As I had
> told I had to write another program of READ statements just to check the
> data. That means the Memory Map window utility is just useless to me. My
> data is there but I can't see it grapically.
>
> - Johari
>
> --- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
> wrote:
> > You should only see zeros in your data area if that's what you
> > specified or reserved. Why don't you post your DATA statements so we
> > can have a look.
> >
> > -- Jon Williams
> > -- Parallax
> >
> >
> >
Original Message
> > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > Sent: Thursday, August 21, 2003 12:28 PM
> > To: basicstamps@yahoogroups.com
> > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> >
> >
> > Yeah I understand the area where my program are stored and where my
> > data are stored. In the Memory Map Window it shows in red my program
> > starts from location $7FF downward. But I don't see a trace of my
> > data. If I used the @DATA reserve directive I could see clearly the
> > area I specified in green but with all "0"s in it. If I specify 64
> > bytes then the 64 bytes location will be coloured green. Is this
> > because of the security feature so others can peek the content of your
>
> > memory?
> >
> > - Johari
> >
> > --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> > <trygve.henriksen@v...> wrote:
> > > Greetings!
> > >
> > > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> > >
> > > > Additionally, as a side note, program memory starts at the bottom
> > > > and
> > > works it
> > > > way up to the top of memory. Data memory starts at the top and
> > > > works
> > > its way
> > > > down to the bottom. If you imagine a case where data memory could
> > > > be
> > > written
> > > > and have the program memory corrupted by it, that is indeed the
> > > > case.
> > > Care
> > > > is therefore recommended when writing to data memory.
> > >
> > > That depends on your definition of 'top' and 'bottom' of memory...
> > > Programs are stored from the highest address possible and towards 0.
> > >
> > > That aside, if you know how much space your data will use you could
> > > reserve it with the DATA statement. (highly recommended)
> > >
> > > :-)
> > > Trygve
> >
> >
> > To UNSUBSCRIBE, just send mail to:
> > basicstamps-unsubscribe@yahoogroups.com
> > from the same email address that you subscribed. Text in the Subject
> > and Body of the message will be ignored.
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> > This message has been scanned by WebShield. Please report SPAM to
> > abuse@p...
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject
> and Body of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> This message has been scanned by WebShield. Please report SPAM to
> abuse@p...
When was the last time you looked at a memory map
in the Windows world?
2. The Stamp IDE's purpose in life is to let you
program the Stamp, and determine when you've
tried to do too much in the stamp. It's not a
'Stamp' simulator. They try to minimize comm
with the Stamp. If you wanted to, you could
easily write a 'Stamp Memory Dumper' program,
which would send the contents of your memory
back to the PC.
3. One of the Stamp's claims to fame is that
it is relatively simple to program, debug, and
apply. Having a continuously updated memory
map could reduce the simplicity and ease of
use, as it is only useful while connected.
--- In basicstamps@yahoogroups.com, "Johari Aziz" <johaziz@y...>
wrote:
> The ideal should be the utility(Memory Map) to show the content at
the
> PRESENT status, every single byte in every address just as other
> Memory Map program back in DOS world. I'm sure people who have work
> with other microcontrollers in DOS would agree. Even back during my
> Apple II time I could monitor every location of my memory. That was
> back in 1980. I think this is the year 2003. Come on you guys at
> Parallax show me some real progress.
>
> - Johari
>
>
> --- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
wrote:
> > Remember that the Memory Map function is to show you what will be
> > downloaded into the Stamp, NOT what your program will do to it
later.
> >
> > -- Jon Williams
> > -- Applications Engineer, Parallax
> > -- Dallas Office
> >
> >
> >
Original Message
> > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > Sent: Thursday, August 21, 2003 10:56 PM
> > To: basicstamps@yahoogroups.com
> > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> >
> >
> > It wasn't a DATA statement. It was WRITE statements. I just used
the
> > @DATA just to check that area of map inititially for testing. As
I had
> > told I had to write another program of READ statements just to
check the
> > data. That means the Memory Map window utility is just useless to
me. My
> > data is there but I can't see it grapically.
> >
> > - Johari
> >
> > --- In basicstamps@yahoogroups.com, "Jon Williams"
<jwilliams@p...>
> > wrote:
> > > You should only see zeros in your data area if that's what you
> > > specified or reserved. Why don't you post your DATA statements
so we
> > > can have a look.
> > >
> > > -- Jon Williams
> > > -- Parallax
> > >
> > >
> > >
Original Message
> > > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > > Sent: Thursday, August 21, 2003 12:28 PM
> > > To: basicstamps@yahoogroups.com
> > > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> > >
> > >
> > > Yeah I understand the area where my program are stored and
where my
> > > data are stored. In the Memory Map Window it shows in red my
program
> > > starts from location $7FF downward. But I don't see a trace of
my
> > > data. If I used the @DATA reserve directive I could see clearly
the
> > > area I specified in green but with all "0"s in it. If I specify
64
> > > bytes then the 64 bytes location will be coloured green. Is
this
> > > because of the security feature so others can peek the content
of your
> >
> > > memory?
> > >
> > > - Johari
> > >
> > > --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> > > <trygve.henriksen@v...> wrote:
> > > > Greetings!
> > > >
> > > > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> > > >
> > > > > Additionally, as a side note, program memory starts at the
bottom
> > > > > and
> > > > works it
> > > > > way up to the top of memory. Data memory starts at the top
and
> > > > > works
> > > > its way
> > > > > down to the bottom. If you imagine a case where data memory
could
> > > > > be
> > > > written
> > > > > and have the program memory corrupted by it, that is indeed
the
> > > > > case.
> > > > Care
> > > > > is therefore recommended when writing to data memory.
> > > >
> > > > That depends on your definition of 'top' and 'bottom' of
memory...
> > > > Programs are stored from the highest address possible and
towards 0.
> > > >
> > > > That aside, if you know how much space your data will use you
could
> > > > reserve it with the DATA statement. (highly recommended)
> > > >
> > > > :-)
> > > > Trygve
> > >
> > >
> > > To UNSUBSCRIBE, just send mail to:
> > > basicstamps-unsubscribe@yahoogroups.com
> > > from the same email address that you subscribed. Text in the
Subject
> > > and Body of the message will be ignored.
> > >
> > >
> > > Your use of Yahoo! Groups is subject to
> > > http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > >
> > > This message has been scanned by WebShield. Please report SPAM
to
> > > abuse@p...
> >
> >
> > To UNSUBSCRIBE, just send mail to:
> > basicstamps-unsubscribe@yahoogroups.com
> > from the same email address that you subscribed. Text in the
Subject
> > and Body of the message will be ignored.
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> > This message has been scanned by WebShield. Please report SPAM to
> > abuse@p...
on at any given time. For us to be able to show you what currently
lives in your EEPROM map would require either a full program simulation
or processor-hogging background process that are constantly dumping the
EE to the PC for you to view; this would have a serious impact program
performance. We're talking about a small, eight-bit embedded processor
here with a few dozen bytes of RAM, not a PC. It's not a fair
comparison you're making.
You can use DEBUG to show the contents -- though I expect it will slow
your contents to a crawl. You just need to write a subroutine that
reads the contents and sends it to the PC using DEBUG. This is as close
as you're going to get to your DOS comaprison. Remember, DOS DEBUG only
dumped the current contents and didn't do a live update -- you were
viewing a snapshot. If you were using a program that was giving you a
live update, then it was a resource-consuming TSR.
-- Jon Williams
-- Applications Engineer, Parallax
-- Dallas Office
Original Message
From: Johari Aziz [noparse]/noparse]mailto:[url=http://forums.parallaxinc.com/group/basicstamps/post?postID=M-BtszwQfPNCfP_dX0SrC0B8ttTFPWzrgC-hKQqQehyWE9SqlPjL1ASVxniHNKqRZU0SBVjn-jZDYhRt]johaziz@y...[/url
Sent: Friday, August 22, 2003 10:20 AM
To: basicstamps@yahoogroups.com
Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
The ideal should be the utility(Memory Map) to show the content at the
PRESENT status, every single byte in every address just as other Memory
Map program back in DOS world. I'm sure people who have work with other
microcontrollers in DOS would agree. Even back during my Apple II time I
could monitor every location of my memory. That was back in 1980. I
think this is the year 2003. Come on you guys at Parallax show me some
real progress.
- Johari
--- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
wrote:
> Remember that the Memory Map function is to show you what will be
> downloaded into the Stamp, NOT what your program will do to it later.
>
> -- Jon Williams
> -- Applications Engineer, Parallax
> -- Dallas Office
>
>
>
Original Message
> From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> Sent: Thursday, August 21, 2003 10:56 PM
> To: basicstamps@yahoogroups.com
> Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
>
>
> It wasn't a DATA statement. It was WRITE statements. I just used the
> @DATA just to check that area of map inititially for testing. As I had
> told I had to write another program of READ statements just to check
> the data. That means the Memory Map window utility is just useless to
> me. My data is there but I can't see it grapically.
>
> - Johari
>
> --- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
> wrote:
> > You should only see zeros in your data area if that's what you
> > specified or reserved. Why don't you post your DATA statements so
we
> > can have a look.
> >
> > -- Jon Williams
> > -- Parallax
> >
> >
> >
Original Message
> > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > Sent: Thursday, August 21, 2003 12:28 PM
> > To: basicstamps@yahoogroups.com
> > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> >
> >
> > Yeah I understand the area where my program are stored and where my
> > data are stored. In the Memory Map Window it shows in red my program
> > starts from location $7FF downward. But I don't see a trace of my
> > data. If I used the @DATA reserve directive I could see clearly the
> > area I specified in green but with all "0"s in it. If I specify 64
> > bytes then the 64 bytes location will be coloured green. Is this
> > because of the security feature so others can peek the content of
your
>
> > memory?
> >
> > - Johari
> >
> > --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> > <trygve.henriksen@v...> wrote:
> > > Greetings!
> > >
> > > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> > >
> > > > Additionally, as a side note, program memory starts at the
> > > > bottom and
> > > works it
> > > > way up to the top of memory. Data memory starts at the top and
> > > > works
> > > its way
> > > > down to the bottom. If you imagine a case where data memory
> > > > could
> > > > be
> > > written
> > > > and have the program memory corrupted by it, that is indeed the
> > > > case.
> > > Care
> > > > is therefore recommended when writing to data memory.
> > >
> > > That depends on your definition of 'top' and 'bottom' of memory...
> > > Programs are stored from the highest address possible and towards
> > > 0.
> > >
> > > That aside, if you know how much space your data will use you
> > > could reserve it with the DATA statement. (highly recommended)
> > >
> > > :-)
> > > Trygve
> >
> >
> > To UNSUBSCRIBE, just send mail to:
> > basicstamps-unsubscribe@yahoogroups.com
> > from the same email address that you subscribed. Text in the
> > Subject
> > and Body of the message will be ignored.
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> > This message has been scanned by WebShield. Please report SPAM to
> > abuse@p...
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject
> and Body of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> This message has been scanned by WebShield. Please report SPAM to
> abuse@p...
To UNSUBSCRIBE, just send mail to:
basicstamps-unsubscribe@yahoogroups.com
from the same email address that you subscribed. Text in the Subject
and Body of the message will be ignored.
Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/
This message has been scanned by WebShield. Please report SPAM to
abuse@p....
wouldn't have any idea what value they are going to input. But I do
know the sequence data from the variables like WRITE 0, byte1, byte2,
Word1, .... and so on. So another section of the program that will
retrieve back the data but not in continous sequence. It will READ it
back one by one into different variables.
It would be easier if I could use variables with array but my earlier
attempt fails because the program didn't allow me to use a large
array, around 64 shared by four variables of 16 each. That's why I
substitute it with WRITE & READ command which could give me more than
64 bytes. The main program only uses 43% of the memory space.
You have to excuse me for being so detail in monitoring every single
bit of my DATA because I came from the machine/assembly language world
for many years. Since I saw that there is a Memory Map window, I
thought I was back in my old world. It would be nice to monitor the
memory content with just a single button while debugging my program.
At this moment I wrote a separate program of READ sequences to monitor
that memory content.
- Johari
--- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...> wrote:
> Wait a minute ... you wrote the program so you should know what's going
> on at any given time. For us to be able to show you what currently
> lives in your EEPROM map would require either a full program simulation
> or processor-hogging background process that are constantly dumping the
> EE to the PC for you to view; this would have a serious impact program
> performance. We're talking about a small, eight-bit embedded processor
> here with a few dozen bytes of RAM, not a PC. It's not a fair
> comparison you're making.
>
> You can use DEBUG to show the contents -- though I expect it will slow
> your contents to a crawl. You just need to write a subroutine that
> reads the contents and sends it to the PC using DEBUG. This is as close
> as you're going to get to your DOS comaprison. Remember, DOS DEBUG only
> dumped the current contents and didn't do a live update -- you were
> viewing a snapshot. If you were using a program that was giving you a
> live update, then it was a resource-consuming TSR.
>
> -- Jon Williams
> -- Applications Engineer, Parallax
> -- Dallas Office
>
>
>
>
Original Message
> From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> Sent: Friday, August 22, 2003 10:20 AM
> To: basicstamps@yahoogroups.com
> Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
>
>
> The ideal should be the utility(Memory Map) to show the content at the
> PRESENT status, every single byte in every address just as other Memory
> Map program back in DOS world. I'm sure people who have work with other
> microcontrollers in DOS would agree. Even back during my Apple II time I
> could monitor every location of my memory. That was back in 1980. I
> think this is the year 2003. Come on you guys at Parallax show me some
> real progress.
>
> - Johari
>
>
> --- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
> wrote:
> > Remember that the Memory Map function is to show you what will be
> > downloaded into the Stamp, NOT what your program will do to it later.
> >
> > -- Jon Williams
> > -- Applications Engineer, Parallax
> > -- Dallas Office
> >
> >
> >
Original Message
> > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > Sent: Thursday, August 21, 2003 10:56 PM
> > To: basicstamps@yahoogroups.com
> > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> >
> >
> > It wasn't a DATA statement. It was WRITE statements. I just used the
> > @DATA just to check that area of map inititially for testing. As I had
>
> > told I had to write another program of READ statements just to check
> > the data. That means the Memory Map window utility is just useless to
> > me. My data is there but I can't see it grapically.
> >
> > - Johari
> >
> > --- In basicstamps@yahoogroups.com, "Jon Williams" <jwilliams@p...>
> > wrote:
> > > You should only see zeros in your data area if that's what you
> > > specified or reserved. Why don't you post your DATA statements so
> we
> > > can have a look.
> > >
> > > -- Jon Williams
> > > -- Parallax
> > >
> > >
> > >
Original Message
> > > From: Johari Aziz [noparse][[/noparse]mailto:johaziz@y...]
> > > Sent: Thursday, August 21, 2003 12:28 PM
> > > To: basicstamps@yahoogroups.com
> > > Subject: Re: SV: [noparse][[/noparse]basicstamps] Nothing on Memory Map Window?
> > >
> > >
> > > Yeah I understand the area where my program are stored and where my
> > > data are stored. In the Memory Map Window it shows in red my program
>
> > > starts from location $7FF downward. But I don't see a trace of my
> > > data. If I used the @DATA reserve directive I could see clearly the
> > > area I specified in green but with all "0"s in it. If I specify 64
> > > bytes then the 64 bytes location will be coloured green. Is this
> > > because of the security feature so others can peek the content of
> your
> >
> > > memory?
> > >
> > > - Johari
> > >
> > > --- In basicstamps@yahoogroups.com, "Trygve Henriksen"
> > > <trygve.henriksen@v...> wrote:
> > > > Greetings!
> > > >
> > > > Fra: Bruce Bates [noparse][[/noparse]mailto:bvbates@u...]
> > > >
> > > > > Additionally, as a side note, program memory starts at the
> > > > > bottom and
> > > > works it
> > > > > way up to the top of memory. Data memory starts at the top and
> > > > > works
> > > > its way
> > > > > down to the bottom. If you imagine a case where data memory
> > > > > could
> > > > > be
> > > > written
> > > > > and have the program memory corrupted by it, that is indeed the
> > > > > case.
> > > > Care
> > > > > is therefore recommended when writing to data memory.
> > > >
> > > > That depends on your definition of 'top' and 'bottom' of memory...
>
> > > > Programs are stored from the highest address possible and towards
> > > > 0.
> > > >
> > > > That aside, if you know how much space your data will use you
> > > > could reserve it with the DATA statement. (highly recommended)
> > > >
> > > > :-)
> > > > Trygve
> > >
> > >
> > > To UNSUBSCRIBE, just send mail to:
> > > basicstamps-unsubscribe@yahoogroups.com
> > > from the same email address that you subscribed. Text in the
> > > Subject
> > > and Body of the message will be ignored.
> > >
> > >
> > > Your use of Yahoo! Groups is subject to
> > > http://docs.yahoo.com/info/terms/
> > >
> > >
> > >
> > >
> > > This message has been scanned by WebShield. Please report SPAM to
> > > abuse@p...
> >
> >
> > To UNSUBSCRIBE, just send mail to:
> > basicstamps-unsubscribe@yahoogroups.com
> > from the same email address that you subscribed. Text in the Subject
> > and Body of the message will be ignored.
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
> >
> > This message has been scanned by WebShield. Please report SPAM to
> > abuse@p...
>
>
> To UNSUBSCRIBE, just send mail to:
> basicstamps-unsubscribe@yahoogroups.com
> from the same email address that you subscribed. Text in the Subject
> and Body of the message will be ignored.
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>
>
> This message has been scanned by WebShield. Please report SPAM to
> abuse@p...
> The ideal should be the utility(Memory Map) to show the content at the
> PRESENT status, every single byte in every address just as other
> Memory Map program back in DOS world. I'm sure people who have work
> with other microcontrollers in DOS would agree.
Err sorry, but I've worked with micro-controllers in the DOS
world and can't agree. I think your mixing apples and oranges
here. If I'm programming an app I want to see the memory map
that I am creating... not the junk current in the eeprom.
What do you propose the memory map should show if the eeprom is
full? Your new application map or the old junk in the eeprom?
Just my two cents... Parallex made the right call here.
Michael Burr
see every bit of data to probe on things. But I'm a programmer I know
exactly where I addressed my data. You may asked if I'm so sure where
it goes than why I like see it in the Memory Map window. This is what
people say double checking. Programming for micro controller is
different with programming software for a normal computer. In normal
computer if thing goes wrong it will just crash and no real harm done.
But with micro controller an error can really cause real world damage.
I'm not talking blinking LEDs here.
The data I'm dealing with is not just few bytes of data. It is large.
I'm pushing the limits of Basic Stamp. I know it is meant to be simple
but that doesn't mean the data can be tinnie winnie. Yes I could
write a series of READ commands and I can check everyone of them.
That's going to be a long scrolling on the DEBUG window. If Parallax
want to give a feature called Memory Map than it should function like
a Memory Map should be. If you give me apples make sure it taste like
apples and not orange. If not, don't call it apple, call it orange.
- Johari
--- In basicstamps@yahoogroups.com, Michael Burr <mburr@b...> wrote:
> Johari Aziz wrote:
> > The ideal should be the utility(Memory Map) to show the content at the
> > PRESENT status, every single byte in every address just as other
> > Memory Map program back in DOS world. I'm sure people who have work
> > with other microcontrollers in DOS would agree.
>
> Err sorry, but I've worked with micro-controllers in the DOS
> world and can't agree. I think your mixing apples and oranges
> here. If I'm programming an app I want to see the memory map
> that I am creating... not the junk current in the eeprom.
>
> What do you propose the memory map should show if the eeprom is
> full? Your new application map or the old junk in the eeprom?
>
> Just my two cents... Parallex made the right call here.
>
> Michael Burr