Author Topic: Axe Parser (Read 552872 times)

ztrumpet · « **Reply #1965 on:** September 25, 2011, 09:50:17 am »

Are Axe Apps automatically signed now? Do we even have to run them through the signer?

alberthrocks · « **Reply #1966 on:** September 25, 2011, 10:54:00 am »

I know for sure that a "Bad Flash" error occurs when you overwrite an archived program. That is, if the target program is prgmOUT, and prgmOUT is archived at the time, when I compile prgmOUTSRC it will say "Bad Flash". Hopefully that helps!

(And the archived prgmOUT for whatever reason disappears, and compilation can occur.)

(This is version 1.0.2, btw)

EDIT: I've confirmed it!

In an emulator ([wx]Wabbitemu), I emulated a TI-83 ROM, and installed Axe 1.0.4 (latest) on it. Then I tried to make a simple program:

Code: [Select]

.XYZ
Disp "HI"

I compiled it, then archived the compiled program. Then I recompiled... nothing bad happened.
I then sent AXERPG.8Xp (an example program), compiled it, and ran it. Then I exited it, archived the compiled program (RPGDEMO.8Xp), and then compiled again.... and got an error!

(UNKNOWN ERROR Code: A429992)
Here's a pic: http://dl.dropbox.com/u/1016340/PublicPictures/AxeBadFlashError104.png

Note that this result may be tainted from the previous compile and execution of a compiled program, so I will retest to make sure this is a valid result.
For now, here's the ROM dump (state save):
http://dl.dropbox.com/u/1016340/AxeBadFlash104.sav

EDIT 2: I've confirmed my prediction - it triggers without any other factors. That is:
Load blank ROM -> Turn on calc -> Send Axe.8Xk -> Send AXERPG.8Xp -> Compile AXERPG.8Xp in Axe -> Archive compiled file RPGDEMO.8Xp -> Try recompiling -> ERROR

Could this be also correlated to program size? It didn't fail with the other tiny program (above).

I've provided the ROM of this error, still at the error screen for better debugging.
http://dl.dropbox.com/u/1016340/AxeBadFlash104_CLEAN_INERR.sav

Quigibo · « **Reply #1967 on:** September 25, 2011, 04:57:52 pm »

Thank you SO much! I can now narrow down the problem.

Axe apps still need to be signed to transfer to another calculator, but at least it won't delete itself.

EDIT: HAHA! I found it! Turns out the problem was that TI's "DelVarArc" bcall re-locks flash again whenever it deletes from flash. My flash unlocking routine was above it, so all I had to do was move it down after that call. Has anyone gotten the random 'r' error yet with 1.0.4?

Eeems · « **Reply #1968 on:** September 25, 2011, 06:16:14 pm »

Quote from: Quigibo on September 25, 2011, 04:57:52 pm

Axe apps still need to be signed to transfer to another calculator, but at least it won't delete itself.

I can't remember if this was asked before, but how long would it take for someone to sign an app on calc, and how much extra space would it take to do so?

DJ Omnimaga · « **Reply #1969 on:** September 25, 2011, 06:26:45 pm »

Hmm by not deleting themselves, do you mean even if you never sign your app it will still remain on your calc forever, just not be sendable to another?

Also glad to see more updates.

alberthrocks · « **Reply #1970 on:** September 25, 2011, 06:48:35 pm »

Quote from: Eeems on September 25, 2011, 06:16:14 pm

Quote from: Quigibo on September 25, 2011, 04:57:52 pm
Axe apps still need to be signed to transfer to another calculator, but at least it won't delete itself.
I can't remember if this was asked before, but how long would it take for someone to sign an app on calc, and how much extra space would it take to do so?

From the DuckSign (on calc app signer) documentation:

Quote from: DuckSign Readme

Hashing the application will take about 4 seconds per page on a TI-83
Plus BE, or about 1 second per page on a TI-83 Plus SE or TI-84 Plus.
Once this is done, computing a new application signature will take
about 50 seconds on a TI-83 Plus BE, or about 20 seconds on a TI-83
Plus SE or TI-84 Plus.

(Yes, you can sign apps on-calc; see http://ourl.ca/7447/149857)

DrDnar · « **Reply #1971 on:** September 25, 2011, 08:44:08 pm »

Xeda seems to love doing math-y things. You should ask her to learn RSA and write an optimized app signer. How long would on-calc app signing take? It could take over ten minutes if you write a really slow signing algorithm, but my gut feeling is that it can probably be done in under a minute.

AngelFish · « **Reply #1972 on:** September 25, 2011, 08:48:09 pm »

Quote from: alberthrocks on September 25, 2011, 06:48:35 pm

Quote from: Eeems on September 25, 2011, 06:16:14 pm
Quote from: Quigibo on September 25, 2011, 04:57:52 pm
Axe apps still need to be signed to transfer to another calculator, but at least it won't delete itself.
I can't remember if this was asked before, but how long would it take for someone to sign an app on calc, and how much extra space would it take to do so?
From the DuckSign (on calc app signer) documentation:
Quote from: DuckSign Readme
Hashing the application will take about 4 seconds per page on a TI-83
Plus BE, or about 1 second per page on a TI-83 Plus SE or TI-84 Plus.
Once this is done, computing a new application signature will take
about 50 seconds on a TI-83 Plus BE, or about 20 seconds on a TI-83
Plus SE or TI-84 Plus.

Is there a particular reason we can't simply get Floppus' permission to distribute ducksign and then bundle it with Axe? For someone who doesn't make apps, I'm not sure I want Axe to use another page if for app signing if that would be necessary.

Eeems · « **Reply #1973 on:** September 25, 2011, 08:51:14 pm »

I wonder if there is enough space left for Axe to add some sort of signing process that can be enabled ( disabled by default ).

Quigibo · « **Reply #1974 on:** September 25, 2011, 09:08:47 pm »

There is enough space (I have about 5KB left on the 2nd page) and I think Floppus suggested I could include it at some point. I just don't think its that high on the priority list right now since how often do you need to send someone an app without a computer? I'd rather spend the time fixing known bugs and you can always add DuckSign to your calculator separately.

Ashbad · « **Reply #1975 on:** September 25, 2011, 09:10:19 pm »

Well considering the only way you distribute Axe-compiled Applications is by loading it through your computer first, I don't see why it's so hard to sign it on the computer (faster...) while you're preparing it for download than while you're testing it on-calc.

flyingfisch · « **Reply #1976 on:** September 25, 2011, 09:11:58 pm »

Ashbad, good to see you again!

DJ Omnimaga · « **Reply #1977 on:** September 25, 2011, 09:12:06 pm »

The problem is that some people do not have a computer at all (or any suitable access to one). JustCause comes to mind.

However, I personally think it should come as an option, not bundled in Axe. People might not want to wait a long while during compiling everytime they're testing something for bugs and they might not like if Axe takes an extra page if they don't need to sign apps.

On a side note what happened to Floppus?

Ashbad · « **Reply #1978 on:** September 25, 2011, 09:13:17 pm »

Quote from: flyingfisch on September 25, 2011, 09:11:58 pm

Ashbad, good to see you again!

Que

Quote from: DJ_O on September 25, 2011, 09:12:06 pm

The problem is that some people do not have a computer at all (or any suitable access to one). JustCause comes to mind.

But then he can't distribute it anyways, so no problem there.

calcdude84se · « **Reply #1979 on:** September 25, 2011, 09:21:23 pm »

Distribution to friends?
But there isn't too much need for integration with the presence of DuckSign.

Author Topic: Axe Parser (Read 552872 times)

ztrumpet

Re: Axe Parser

alberthrocks

Re: Axe Parser

Quigibo

Re: Axe Parser

Eeems

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

alberthrocks

Re: Axe Parser

DrDnar

Re: Axe Parser

AngelFish

Re: Axe Parser

Eeems

Re: Axe Parser

Quigibo

Re: Axe Parser

Ashbad

Re: Axe Parser

flyingfisch

Re: Axe Parser

DJ Omnimaga

Re: Axe Parser

Ashbad

Re: Axe Parser

calcdude84se

Re: Axe Parser