0 Members and 3 Guests are viewing this topic.
Quote from: ScoutDavid on November 27, 2010, 09:31:32 amReturning to WikiTI:This topic is inside the Assembly Programming Forum... WikiTI is for Assembly only?I'm quite confused now, since I made Axe Parser's page :SWikiTI is for whatever we make it. It is mostly focused on assembly programming because that's where third-party documentation is most needed - TI's documentation barely scratches the surface of what assembly language can do. But there's no reason to exclude other languages. I don't think there's a need to document the Axe language itself - that's what the official documentation is for - but programming tips, example code, and tutorials would be very much welcome.
Returning to WikiTI:This topic is inside the Assembly Programming Forum... WikiTI is for Assembly only?I'm quite confused now, since I made Axe Parser's page :S
Quote from: FloppusMaximus on November 29, 2010, 11:26:16 pmQuote from: ScoutDavid on November 27, 2010, 09:31:32 amReturning to WikiTI:This topic is inside the Assembly Programming Forum... WikiTI is for Assembly only?I'm quite confused now, since I made Axe Parser's page :SWikiTI is for whatever we make it. It is mostly focused on assembly programming because that's where third-party documentation is most needed - TI's documentation barely scratches the surface of what assembly language can do. But there's no reason to exclude other languages. I don't think there's a need to document the Axe language itself - that's what the official documentation is for - but programming tips, example code, and tutorials would be very much welcome.Thanks for the explanation, BUT this is the Assembly category, what, why?
About that : http://wikiti.brandonw.net/index.php?title=83Plus:Ports:01In the example, a "xor" must be used, not an "and".
Also, a little paragraph about delays between writing & reading could be necessary, don't you think ?For what we had tested, maximum cycles was 6 in cpu speed 0, and 29 in any other (about a dozen models tested).The cse has longer delays, but we were only able to test one calc.
$FD and $FD = $FD, right ?
I'm of the opinion that resetting the group port is not necessary. Axe's direct key input routine has never done so, and if it didn't work, I'm sure we'd have heard about it from any one of its hundreds of users by now. (I did actually hear about problems a few times, but simply upping the delay seemed to fix any issues)For reference, the current version of the direct key input routine explicitly waits for a fairly generous 40 cycles, or if you want to count the cycles of delay in the out/in instructions themselves, 51 cycles.
Quote from: Runer112 on May 12, 2014, 08:33:01 amI'm of the opinion that resetting the group port is not necessary. Axe's direct key input routine has never done so, and if it didn't work, I'm sure we'd have heard about it from any one of its hundreds of users by now. (I did actually hear about problems a few times, but simply upping the delay seemed to fix any issues)For reference, the current version of the direct key input routine explicitly waits for a fairly generous 40 cycles, or if you want to count the cycles of delay in the out/in instructions themselves, 51 cycles.Wow that's a lot. is it for 15MHz compatibility ?