[A83] Re: App signing
[Prev][Next][Index][Thread]
[A83] Re: App signing
All but the last page will be filled full to 16K. So if the app is only one
page, then it wont be filled at all. I agree that the main gain here is
transmission time. As for writes to Flash, the way it works, the entire
Flash page is put through an erase cycle (clearing all bytes to 0FFh), and
then all the sent bytes are set on the page. In terms of Flash-ROM life,
it's only the erase cycles that matter.
-Dan Englender
----- Original Message -----
> Actually, it seems that apps aren't filled up to the 16kb barrier on the
PC.
> This would make sense, because making apps larger than they need to be
would
> increase transmission time, and possibly write more bytes to the flash
> (although these bytes may be written by the ROM anyway, depending on how
> it's implemented)
>
> Kirk
>
> -----Original Message-----
> From: assembly-83-bounce@lists.ticalc.org
> [mailto:assembly-83-bounce@lists.ticalc.org]On Behalf Of Henk Poley
> Sent: Tuesday, June 26, 2001 8:59 AM
> To: assembly-83@lists.ticalc.org
> Subject: [A83] Re: App signing
>
>
>
> > Van: Gavin Olson <gtolson@snet.net>
> >
> > >> Forgot to mention, I asked TI for the rabsig source (calcsig.c),
> > >> now to see if I really get it from them :-)
> > >
> > >I see you have looked some further inside the exes themselves, also
> found
> > >the html-page with a commercial about lipstick? Any idea what it's
doing
> > >there? Probably a joke from Ti programmers ;-)
> > >
> > >Or just to fill their fillapp-program?
> >
> > Whatever it takes to fill the full 16K :-)
>
> Uhm, sorry, but the fillapp program is a DOS32 program, not a Flash-app...
> It's probably used to fill your .hex file up to the next 16k 'barrier'. If
> you want to see what I'm talking about, download the files Hyperbyte send
a
> link to, and hex-edit (..read-only..) the fillapp.exe (btw: it's somewhat
> illegal, but since you probably don't know anything about x86
> (dis)assembly, never mind.)
>
> Henk Poley
>
>
>
>
>
References: