Author Topic: Proposition about the way of Display Memory  (Read 5284 times)

Mucter

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
Proposition about the way of Display Memory
« on: October 14, 2009, 07:17:46 pm »
Hi

In Display Memory menu,
Flash Magic sends like following to target.
....
:05000004FEB0FEBF008C
:05000004FEC0FECF006C
....

In this way it takes so many time because of short record length(16bytes)
My proposition is that Flash Magic just sends
:050000040000FFFF00F9
(record length is 0x10000 bytes)
to target.

from my experiment,( in 9600 bps)
present way: 4:45
proposal way: 2:50

regards,
Mucter.


Andy Ayre

  • ESAcademy Staff
  • Sr. Member
  • *****
  • Posts: 2169
    • View Profile
    • Embedded Systems Academy, Inc.
    • Email
Re: Proposition about the way of Display Memory
« Reply #1 on: October 15, 2009, 08:40:26 am »
The problem is that users want to see something rather than sitting and waiting for 2 minutes 50 seconds. I think a better solution might be to subdivide the flash block into smaller blocks so users can choose which area to quickly look at.

Andy
Embedded Systems Academy, Inc.
support at esacademy dot com

Mucter

  • Jr. Member
  • **
  • Posts: 20
    • View Profile
Re: Proposition about the way of Display Memory
« Reply #2 on: October 15, 2009, 06:09:28 pm »
Hi Andy.

It's understandable you said. I was thinking so after I posted.
thanks.

But "File -> Save as" Command use same 16bytes command.
I think that this command would use rather 1-all comand than 16bytes command.

"1-all" means that user specified range(textbox from 0x___ to 0x____ ).

Mucter.

Andy Ayre

  • ESAcademy Staff
  • Sr. Member
  • *****
  • Posts: 2169
    • View Profile
    • Embedded Systems Academy, Inc.
    • Email
Re: Proposition about the way of Display Memory
« Reply #3 on: October 16, 2009, 08:56:15 am »
We will add this to the list of possible improvements for future releases. Thanks!

Andy
Embedded Systems Academy, Inc.
support at esacademy dot com