0 Members and 2 Guests are viewing this topic.
In order to try and test a new feature for Assemblex, I'd like to know how to create an application that displays HELLO WORLD. I can do it in Axe easily, but I want the Assembly code. Also, can someone tell me a bit about header.asm/etc. files needed to code a flash application?
Quote from: Scout on February 04, 2011, 10:50:24 amIn order to try and test a new feature for Assemblex, I'd like to know how to create an application that displays HELLO WORLD. I can do it in Axe easily, but I want the Assembly code. Also, can someone tell me a bit about header.asm/etc. files needed to code a flash application?Well, PutS doesn't work in apps, so your going to have to use PutC in your own function like PutSApp. Also the header file is very important. TI has a header application you can use.
.nolist #include "ti83plus.inc".list.org $4000 db 080h, 00Fh db 000h, 000h, 000h, 000h db 080h, 012h db 001h, 004h db 080h, 021h db 001h db 080h, 031h db 001h db 080h, 048h db "Hello", 000h, 000h, 000h db 080h, 081h db 001h db 080h, 090h db 003h, 026h, 009h, 004h db 01Ah, 086h, 054h, 0E9h db 002h, 00Dh, 040h, 0A1h, 06Bh, 099h, 0F6h, 059h, 0BCh, 067h db 0F5h, 085h, 09Ch, 009h, 06Ch, 00Fh, 0B4h, 003h, 09Bh, 0C9h db 003h, 032h, 02Ch, 0E0h, 003h, 020h, 0E3h, 02Ch, 0F4h, 02Dh db 073h, 0B4h, 027h, 0C4h, 0A0h, 072h, 054h, 0B9h, 0EAh, 07Ch db 03Bh, 0AAh, 016h, 0F6h, 077h, 083h, 07Ah, 0EEh, 01Ah, 0D4h db 042h, 04Ch, 06Bh, 08Bh, 013h, 01Fh, 0BBh, 093h, 08Bh, 0FCh db 019h, 01Ch, 03Ch, 0ECh, 04Dh, 0E5h, 075h db 080h, 07Fh db 000h, 000h, 000h, 000h db 000h, 000h, 000h, 000h db 000h, 000h, 000h, 000h db 000h, 000h, 000h, 000h db 000h, 000h, 000h, 000h bcall(_clrScrnFull) bcall(_homeUp) bcall(_clrTxtShd) ld hl, textloop: ld a, (hl) or a jr nz, notDone bcall(_newLine)loop2: bcall(_getCSC) halt or a jr z, loop2 bcall(_jForceCMDNoChar)notDone: bcall(_putC) inc hl jr looptext: .db "Hello world", 0.end
80 0F 00 00 00 00 80 12 01 04 80 21 01 80 31 01 80 48 48 65 6C 6C 6F 00 00 00 80 81 01 80 90 03 26 09 04 1A 86 54 E9 02 0D 40 A1 6B 99 F6 59 BC 67 F5 85 9C 09 6C 0F B4 03 9B C9 03 32 2C E0 03 20 E3 2C F4 2D 73 B4 27 C4 A0 72 54 B9 EA 7C 3B AA 16 F6 77 83 7A EE 1A D4 42 4C 6B 8B 13 1F BB 93 8B FC 19 1C 3C EC 4D E5 75 80 7F 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 EF 46 45 EF 58 45 EF 4C 45 21 A3 40 7E B7 20 0D EF 2E 45 EF 18 40 76 B7 28 F9 EF 27 40 EF 04 45 23 18 E9 48 65 6C 6C 6F 20 77 6F 72 6C 64 00(copied from the app compiled as a program)
The thing about apps, though, is that they come out as 16384 byte multiples any way you go about it. And Are you typing this into your calculator by hand? I don't see how you could do that for apps.
One thing, though: when you open applications in Notepad, aside from a bit of gibberish you can see the HEX fine. I assume this means disassembling wouldn't be as hard as with 8xp files, right?
Oh I mean, take a 8xk file, right-click it, then click open with..., then select Notepad from the list (or search for it). WHen you open the 8xk file in notepad, it shows a large string of hexadecimal.