Started by Bruce Abbott, 12:59, 16 January 14
0 Members and 1 Guest are viewing this topic.
Quote from: TFM on 19:50, 16 January 14One suggestion: It would be great if your assembler can assemble itself without the necessity of using an assembler on the PC side. Just an idea.
QuoteSuggestion two: Would be nice if you could include the second register set of the Z80.
Quote from: TFM on 23:40, 17 January 14The limitation of the label to six letters is indeed a bit small. Is it due to the way the editor works?Could it be expanded in some way?
Quote from: TFM on 20:10, 18 January 14Oh, I see, that's not as easy as I did hope. I guess six characters for labels are fine too. Since one label uses 8 bytes it fit's nicely a 256 page (32 labels). If you use eight characters, then the label need 10 bytes and one of them would reach over the page end, which may cause problems (if the assembler uses INC L instead of INC HL).
Quote from: Hicks on 14:31, 21 January 14Do you consider it as a "work in progress" (= it's possible to change some things according to the needs of the users) or a "quasi-final version" (= no major changes are planed)?
Quote from: Hicks on 15:47, 21 January 14A first question: if I load the "hello.asm" source code (L => hello.asm) and assemble it in RAM (A => 2). Then I switch in debug mode (D) and execute it (.#8000). It works, but when I try to go back to the assembler (A) Champ say to me that my source code is corrupted and clean it. Is it normal?
QuoteA suggestion: a shortcut will be nice, for exemple : from the assembler, I press "CRTL+A" and he do "A => 2 + D + .#8000. A "ENT $" (cf. DAMS) instruction will be nice to give the entry adress of the source code (and then we can just type "." without adress).
QuoteIt seems also that the "math" is a weak point if only simple additions and substractions are tolerated... We often need multiplications, divisions and "complex" operations with labels (i.e. adr/256+#80) to make the code more flexible/dynamic.
Quote from: Bruce Abbott on 17:18, 21 January 14... Perhaps the ORG directive could also set the entry address?
ORG #8000,start;byte DEFB 0word DEFW 0;start PUSH AF PUSH BC ...
Quote from: Hicks on 18:21, 21 January 14is it possible to give 2 parameters to ORG? The first will be the starting address of the source and the second the set entry address?
Quote from: Hicks on 13:01, 22 January 14you wrote that #8000-#9FFF area must be free.
QuoteIs it possible to move it in the expanded RAM, I mean, if I have a 512kb CPC can I put this area out of the base 128kb in order to have the full memory free to use?
Quote- same question for the source code: can I store it out of the base 128kb?
Quote from: TFM on 19:39, 22 January 14Well... for CC the source exceeds 500 KB by far
QuoteDunno if 32 KB is enough, maybe it could be more dynamic?
QuoteMost of the other utilities use E-RAM from C4-C7, but this is very few, so you could disregard it.
QuoteNOTE: Assembling to RAM is potentially dangerous. To avoid overwriting memory used by CHAMP or the OS etc., make sure that an appropriate ORG directive has been entered. The Info command will tell you what memory areas CHAMP is using. The area from &8000 to &9FFF should be free.
Quote(only a masochist uses an inferior tool when they have access to a better one).
Quote from: Hicks on 17:57, 28 January 14In the notice, I read:But you say that #8000 to #9000 is free... So I think it's a little mistake in the notice and imagine that #9000 to #9FFF is reserved to CHAMP ?
QuoteA nice improvement of your "INCB" directive will be to allow 1 or 2 parameters like :- address entry of the file
Quote- bank number (by bank I mean #C4, #C7, i.e. bloc of 16kb.
QuoteI think you called it "page" in another post... For me a "page" is a bloc of 4 banks, i.e. 64kb.
QuoteAnd the top of the top would be to detect if the file has already been loaded in order to load all the files only the first time we assemble our code!
Quote"WRI" directive is a good idea too.
QuoteDoes it mean that you think that it's masochist to use Champ today instead of cross-assembler?
Page created in 0.338 seconds with 52 queries.