Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - the_mad_joob

Pages: 1 ... 21 22 [23] 24
331
TI Z80 / Re: asmdream is waking up...
« on: May 04, 2011, 07:53:55 pm »
Hey guys...

@ Xeda112358 :
- about page spaning :
Thx 4 the answer =]
I wanted to be sure cause i already knew that group variables were (supposed to be) limited to 2 pages at max (meaning data location may be adjusted by the os if crossing a 3rd one).
- about inc file :
Well, that's one of my issues, since asmdream syntax is specific.
I'll take care of this when i'm sure the whole algo works.
I was thinking of building some kind of syntax converter but i won't forget your proposition if i encounter some issues =]

@ calc84maniac :
Thx 4 the routine =]
Mine is 2 bytes bigger but i think i'll leave it as it is for one reason :
It is called after pointer modifications (not only incrementations).
This saves lots of jumps, especially when you need to alter the pointer without accessing data.

@ willrandship :
- about tokens :
I already thought about it before starting the project but unfortunately, only 1-character tokens will be authorized.
Mainly because other ones may definitely not match the directives functions (custom would have been nice but no time for this).
Also, i didn't want the user to spend his life in menus or catalog.
In fact, except when using the token2ascii feature, all the needed tokens can be accessed without entering any menu, for efficiency purpose.
- about the marker :
Thx for reminding it to me !
I already thought about it but for an unknown reason, the idea vanished from my priority stack =]

Have to go... notepad is calling me =]

332
TI Z80 / Re: asmdream is waking up...
« on: May 04, 2011, 01:40:37 pm »
Modified mac_call a bit.
It now also includes a backup of the current program counter value.
This will allow the usage of local labels inside macros definitions =]

333
TI Z80 / Re: asmdream is waking up...
« on: May 03, 2011, 09:46:42 pm »
Yo...

Today, written mac_call & mac_return.
Those routines both allow jumps through sources & includes and increment/decrement a custom stack pointer.
This stack is used to backup calls & definitions pages/offsets before the jumps, in order for the nesting feature to be functional.
Also, it may later allow parameters passing =]
Imagine the possibilities with for example 3 nested macros, the 3rd one using the 1st one's parameters...

Have to do the same for equates now.
After that, i think i will have the necessary routines to code the part of the main which calculates the size of the output program and reserves it in ram (or displays an error if not enough available).

Btw, i have a little question.
If i create a huge basic program (data>16385 bytes more precisely) and then archive it, is there a chance that it will span more than 2 rom pages ?
I'm asking because if this is not the case, this could reduce the size of one of my routines a little bit (and additionally accelerate the reading of archived sources/includes).

334
TI Z80 / Re: asmdream is waking up...
« on: May 03, 2011, 02:26:02 am »
Thx, but i'm afraid the word "luck" has no meaning in zilog world =]

335
TI Z80 / Re: asmdream is waking up...
« on: May 03, 2011, 01:36:53 am »
Thx =]

Here's a summary of what's done for now :

*****

DISPLAY
title screen
main interface
status
basic error messages

KEY INPUT
basic actions
target source input

KERNEL
auto-detection of sources/includes locations (ram/flash)
sources/includes reading directly from flash
basic directives
can locate the matching equate definition from its call
can locate the matching macro definition from its call (even if it has some custom parameters)
complex token strings conversion (multiple bases and arithmetic operators mixed in a single expression)

MISC
z80 ops file matching asmdream syntax

*****

So, a lot of work to write all this but the worse is yet to come...

Anyway, i won't forget to share the news =]

336
TI Z80 / Re: asmdream is waking up...
« on: May 02, 2011, 02:29:57 pm »
Hey dj...

Writing source code directly from the tios and macros enhancements may be a good start =]
And yeah, that is my first "serious" z80 project but i'm already familiar with asm programming (hopefully).

Cu around...

337
TI Z80 / Re: asmdream is waking up...
« on: May 02, 2011, 02:07:46 pm »
Already knew the existence of mimas but thx for the info =]
Didn't try it (yet) but that looks like a great option for now.

Like i said, i wanted to write my own for fun and challenge.

Don't know if mimas (or any other compiler) can do this but i intend to enlarge the way macros work to the maximum, including labels usage and parameters nesting.
If i succeed in this part of the code, the possibilities may be huge, like let's say, an easy way to create a high level programming language.
But, writing this kind of loops may be a true pain without anything to smoke...
Hopefully, i have prodigy =]

Thx for support guys...

P.S. : Some more peanuts ! Tradition sometimes has its good points =]

338
TI Z80 / asmdream is waking up...
« on: May 02, 2011, 05:18:00 am »
hey there...

I'm quite new to these forums but i thought it would be nice to share the thing around :

A few weeks ago, i digged out a project that was sleeping for too long.
It's called "asmdream" and is, in fact, an (other) on-calc asm compiler for the 8X+ series.
So, nothing revolutionnary, but it has its particularities (wanted to make something new).

The main challenge here was to make it able to convert token-based sources directly into machine code.
For the ease of use, i was forced to define a simplified syntax because of the large font usage and lack of readability of the tios prgm editor.
But don't worry, i made it very instinctive so we're not so far from tasm.

It is supposed to handle, at least :
- all z80 instructions (undocumented included)
- includes
- labels
- equates (nesting allowed)
- macros with parameters (nesting allowed)
- bases conversions : binary/decimal/hexadecimal/ascii/token
- arithmetic operators : positive/negative/addition/substraction
- read from flash (sources/includes)

For obvious reasons, i do my best to optimize it in favor of space (about 2K for now) but i'm still amazed how fast it does the job.
I work on it many hours per day but it's still hard to tell when it'll see the light (progress maybe around let's say... 50%).

I'll use this thread to post news and (hope not) ask for help.
Also, don't hesitate if you've some questions/suggestions.

cu around =]

339
News / Re: PolyPatch84 released
« on: April 03, 2011, 08:30:30 pm »
Hey crit,

You're totally right when u say that the self-test should not alter the flash rom.
The thing is : it actually doesn't (and has never did) !
It is a mistake from the beginning as penguin already mentioned it on this thread (page 1) but also on tibank (He posted a comment on polypatch84 news page.).
Actually, penguin's fix removes the groups deletion from ptt (not only the groups in fact, my mistake there).

If this can help, i made some more accurate tests to see exactly which patch does what :

BPM

      PTT - [<]+[>]+[ON] - 2.40>2.55
X X locks the execution/edition of all prgms/apps
 XX deletes all variables from vat, archived or not, except for prgms/apps
   X creates empty predefined lists (L1-L6) in vat if not already existing
   X sets some system settings to the values inputed by the user

     TEACHER RESET - [8]+[5|2]+[ON] - 2.41>2.55
X   deletes all variables from vat, archived or not, except for singapore language apps if [2] used
X   creates empty predefined lists (L1-L6) in vat

     TESTGUARD2 - probably a ti program which has the same effect as ptt
X   locks the execution/edition of all prgms/apps

B = patched by brandon - "patchptt" - 2.40>2.53
P = patched by thepenguin77 - "nodel" - 2.43>2.53
M = patched by mapar - "ptterase" - 2.43>2.53

Note about mapar's patch :
It's the only one that fully cancels all ptt effects (including those nasty functions disabling on 2.53) but it has a little drawback (for students).
At the 1st ptt screen, the input of system settings works but has no effect on the actual values (part of the patch).
The problem is that, on the 2nd screen (ptt complete), the original ptt code displays the actual ones.
So, if the teacher sets different values than the actual ones, he may notice that his input has been ignored (if he takes enough time to read the 2nd screen).

Now, it's up to you to see what is better for polypatch84 =]

340
News / Re: PolyPatch84 released
« on: April 03, 2011, 02:42:29 pm »
Well done crit for having figured it out =].

Maybe brandon included some kind of usb packets check routine at a time and patched this os instead of a clean one, by mistake.
If not, i agree on the fact that it isn't that safe because the probability that something else may be broken remains.
Anyway, putting a ")" at the end of "for" loop declarations isn't that difficult until brandon figures it out...

I know you're running out of time but here is some little feedback for polypatch84 :

- Self-test group deletion fix :
To my opinion, this one should be replaced by mapar's PTT patch (currently available for 2.43 and 2.53).
It's a lot more complete in a way that it prevents any type of data to be altered in RAM/FLASH, not only groups.
In addition, PTT mode settings modifications are 100% ignored.
In fact, it only displays the fake "reset complete" screen and ignores everything PTT normally does.
It does not remove "[8]+[5|2]+[ON]" but his patch was originally written to cohabit with brandon's one, which does this (mentioned in mapar's readme).
I personnaly tested it and i can say the combination of brandon+mapar PTT patchs works like a charm.
Anyway, if you decide to change nothing, it should definitely be renamed "PTT group deletion fix", at least for clarification purpose.

341
News / Re: PolyPatch84 released
« on: April 03, 2011, 09:29:40 am »
Yeah, we always miss this precious time...

If only i could at least check if the strange display is already there in brandon's patched 2.41 (for glitch fix only).
I'm interested if someone knows how to succeed in transferring it to real hardware.

By the way, i noticed that brandon's patched 2.53 (xlib) is also 710315 bytes long (impossible to send too).
Any idea why brandon's patched oses are cut like this ?

342
News / Re: PolyPatch84 released
« on: March 28, 2011, 04:22:19 pm »
Yeah, brandon seem to have a dark side...
But who does not =]

Thx again DJ.

343
News / Re: PolyPatch84 released
« on: March 28, 2011, 03:12:19 pm »
I can fully understand why the link's been removed and if there's someone to be sorry, that's me and nobody else =S
Starting from now, i'll think twice before posting such data.
I promise =]

344
News / Re: PolyPatch84 released
« on: March 28, 2011, 06:11:18 am »
Oh, didn't even know the existence of the [edit by ztrumpet to remove link] directory =S
Thx to ya critor =]
Strangely, ti-connect enters an infinite loop when i try to send it to my calc ([Ctrl]+[Alt]+[Del] required).
It's probably because the original 2.41 os is 710374 bytes long and brandon's patched one is only 710315, dunno.

Anyway, here are my tests results :

The "counter" is there too in the polypatched os 2.40 & 2.41.

Sended the following original patchs to a 2.43 clean os : version/flash/addr/defrag.
They seem to cohabitate well and the "counter" is not there at all.
So we can say those are not directly responsible for the "counter"'s presence.

Like i said, i wasn't able to test the "for glitch" original patch but it's the last one to test so there's a great chance it may be implicated.

With what we know, we can now say that the cause of this strange display is either :
- The "for glitch" fix itself, which would mean that brandon did something wrong (because the glitch itself has nothing to do with usb transfers).
- An incompatibility between the "for glitch" fix and one or more of the following fixes : version/flash/addr/defrag (maybe a part of the os modified by more than one fix).
- An error made by crit while compiling the patchs (maybe a part of the os modified but not initially meant to be patched).

345
News / Re: PolyPatch84 released
« on: March 28, 2011, 03:57:27 am »
Thx for the numerical peanuts Ashbad =]

I'm gonna help to identify in which patch the responsible code is included.
By chance, most of the original patchs are compatible with 2.43 so i'll apply them separately and test some transfers.
For now, i can logically say that it's one of those : version/basic/flash/addr/defrag.

After having identified the patch, i'll test it on the other compatible oses to know if it's the result of some kind of incompatibility or not.

About the "for glitch" fix, there is no way i can find the appropriate file in brandon's "calcstuff" directory.
Dunno if it was removed but otherwise, i'm interested if anyone knows the exact file name...

Pages: 1 ... 21 22 [23] 24