« previous next »
Pages: 1 [2] 3 4   Go Down

Author Topic: Hexadecimal Assembly Programming  (Read 21962 times)

0 Members and 1 Guest are viewing this topic.

Ashbad

  • Guest
Re: Hexadecimal Assembly Programming
« Reply #15 on: January 22, 2011, 07:55:37 pm »
writing without system calls is more fun.  But eventually leads to you getting cocky and writing a shell to beat the big ones like MOS/DCS7.  That's what happened to Lo-C and AshbadOS (both were by me, and both failed.  Lo-C was more of a shell however that was meant to allow the user extreme ease in logic and structure functions, like in the language C)

Yeah I used to be hex but moved out.  though it was quite fun :)
Logged

Offline Xeda112358

  • they/them
  • Moderator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 4704
  • Rating: +719/-6
  • Calc-u-lator, do doo doo do do do.
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #16 on: January 22, 2011, 08:00:43 pm »
Yeah, I'll admit I have been getting kind of "cocky," but I do prefer to make my own routines if they are similar but better than the ROM calls. As for making a shell... I might make one as an added feature, but I am not all that great at actually programming in assembly. I can make calls and routines, but to actually make running programs... that is a bit different.
And programming in hex is fun! It's a lot easier for me to work with, so I try to stick with that. I do absolutely love and appreciate Assemblex because it makes it easier for me to use mnemonics, too.
Logged

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #17 on: January 22, 2011, 08:03:48 pm »
The great thing about hex is that it makes a lot more sense than Assembly does. It also eliminates the need for an Assembler, which are always problematic for me. The downside is calculating jumps...
* Qwerty.55 just realized that his hex has been throwing illegal instruction errors and he didn't even realize it.
« Last Edit: January 22, 2011, 08:04:45 pm by Qwerty.55 »
Logged
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline Munchor

  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6199
  • Rating: +295/-121
  • Code Recycler
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #18 on: January 22, 2011, 08:04:49 pm »
Quote from: Qwerty.55 on January 22, 2011, 08:03:48 pm
The great thing about hex is that it makes a lot more sense than Assembly does. It also eliminates the need for an Assembler, which are always problematic for me. The downside is calculating jumps...

And also memorizing (downside). When programming in Hex I always use all-program labels instead of byte-based labels.
Logged

Offline Xeda112358

  • they/them
  • Moderator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 4704
  • Rating: +719/-6
  • Calc-u-lator, do doo doo do do do.
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #19 on: January 22, 2011, 08:05:30 pm »
Completely and fully agreed. Luckily, the calc has 16 chars to a line which makes it a little easier. Every two lines adds 10h to the address.
Logged

souvik1997

  • Guest
Re: Hexadecimal Assembly Programming
« Reply #20 on: January 22, 2011, 08:17:33 pm »
Quote from: Scout on January 22, 2011, 08:04:49 pm
Quote from: Qwerty.55 on January 22, 2011, 08:03:48 pm
The great thing about hex is that it makes a lot more sense than Assembly does. It also eliminates the need for an Assembler, which are always problematic for me. The downside is calculating jumps...

And also memorizing (downside). When programming in Hex I always use all-program labels instead of byte-based labels.
Do you mean that you are doing "jp XXXX" instead or "jr XXXX"? The JP opcode uses one more byte than the JR oprcode, so it's not very efficient to always use that. :/

@Qwerty.55: Programming the calculator using hexadecimal machine code instructions is exactly the same as programming the calculator with assembly instructions, so I don't see how that makes more sense.
Logged

Offline Munchor

  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6199
  • Rating: +295/-121
  • Code Recycler
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #21 on: January 22, 2011, 08:18:44 pm »
Quote from: souvik1997 on January 22, 2011, 08:17:33 pm
Do you mean that you are doing "jp XXXX" instead or "jr XXXX"? The JP opcode uses one more byte than the JR oprcode, so it's not very efficient to always use that. :/

It is definetely not the optimized way to do it.
Logged

Offline AngelFish

  • Is this my custom title?
  • Administrator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 3242
  • Rating: +270/-27
  • I'm a Fishbot
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #22 on: January 22, 2011, 08:23:47 pm »
Quote from: souvik1997 on January 22, 2011, 08:17:33 pm
@Qwerty.55: Programming the calculator using hexadecimal machine code instructions is exactly the same as programming the calculator with assembly instructions, so I don't see how that makes more sense.

The way the equates are designed on some systems makes more sense than the mnemonics. For example MOV Rm, Rn is 6nm3, which is more logical.
Logged
∂²Ψ    -(2m(V(x)-E)Ψ
---  = -------------
∂x²        ℏ²Ψ

Offline DJ Omnimaga

  • Clacualters are teh gr33t
  • CoT Emeritus
  • LV15 Omnimagician (Next: --)
  • *
  • Posts: 55943
  • Rating: +3154/-232
  • CodeWalrus founder & retired Omnimaga founder
    • View Profile
    • Dream of Omnimaga Music
Re: Hexadecimal Assembly Programming
« Reply #23 on: January 23, 2011, 02:47:44 am »
The problem in hex though is writing extremly massive games. I think reading E:SoR code in hex would start being hard. O.O
Logged

Offline Munchor

  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 6199
  • Rating: +295/-121
  • Code Recycler
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #24 on: January 23, 2011, 04:55:22 am »
Quote from: DJ Omnimaga on January 23, 2011, 02:47:44 am
The problem in hex though is writing extremly massive games. I think reading E:SoR code in hex would start being hard. O.O

But even though, Zeda made an Application :D
Logged

Offline Xeda112358

  • they/them
  • Moderator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 4704
  • Rating: +719/-6
  • Calc-u-lator, do doo doo do do do.
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #25 on: January 23, 2011, 11:13:20 am »
Hehe...
<.<
>.>
Time for another App...

Oh, and it actually isn't too difficult to understand hex once you've used it long enough. I've been disassembling the TI-OS just by reading the hex and I've learned some useful things (like how to tell what model calc is being used, which areas of extra RAM are off limits, how ROM calls are handled) that kind of thing. If you happen to know which page the ROM call location is on, you can save a little speed (maybe a few hundred T-States) at the cost of a few extra bytes.

But yeah, I'm not saying it's easy, though. It makes my brain hurt, but I can get through maybe a thousand bytes of code per hour, give or take depending on how complex the routines are. That is what I had to do when I made the font hook...  ._.
Logged

Offline Binder News

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 785
  • Rating: +46/-3
  • Zombie of Tomorrow
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #26 on: January 23, 2011, 11:33:45 am »
You are amazing. O.O
Logged
Spoiler For userbars:







Hacker-in-training!   Z80 Assembly Programmer     Axe Programmer
C++ H4X0R             Java Coder                           I <3 Python!

Perdidisti ludum     Cerebrum non habes

"We are humans first, no matter what."
"Fame is a vapor, popularity an accident, and riches take wings. Only one thing endures, and that is character."
Spoiler For Test Results:




Offline Xeda112358

  • they/them
  • Moderator
  • LV12 Extreme Poster (Next: 5000)
  • ************
  • Posts: 4704
  • Rating: +719/-6
  • Calc-u-lator, do doo doo do do do.
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #27 on: January 23, 2011, 11:43:52 am »
Nah, that's just what you can do when you don't have internet (meaning you have LOTS of time and no other means).
Logged

Offline Deep Toaster

  • So much to do, so much time, so little motivation
  • Administrator
  • LV13 Extreme Addict (Next: 9001)
  • *************
  • Posts: 8217
  • Rating: +758/-15
    • View Profile
    • ClrHome
Re: Hexadecimal Assembly Programming
« Reply #28 on: January 23, 2011, 12:37:55 pm »
Quote from: Xeda112358 on January 23, 2011, 11:13:20 am
Hehe...
<.<
>.>
Time for another App...

Oh, and it actually isn't too difficult to understand hex once you've used it long enough. I've been disassembling the TI-OS just by reading the hex and I've learned some useful things (like how to tell what model calc is being used, which areas of extra RAM are off limits, how ROM calls are handled) that kind of thing. If you happen to know which page the ROM call location is on, you can save a little speed (maybe a few hundred T-States) at the cost of a few extra bytes.

But yeah, I'm not saying it's easy, though. It makes my brain hurt, but I can get through maybe a thousand bytes of code per hour, give or take depending on how complex the routines are. That is what I had to do when I made the font hook...  ._.

You're literally reading numbers as words O.O
Logged



Offline Binder News

  • LV8 Addict (Next: 1000)
  • ********
  • Posts: 785
  • Rating: +46/-3
  • Zombie of Tomorrow
    • View Profile
Re: Hexadecimal Assembly Programming
« Reply #29 on: January 23, 2011, 12:42:05 pm »
Quote from: Deep Thought on January 23, 2011, 12:37:55 pm
Quote from: Xeda112358 on January 23, 2011, 11:13:20 am
Hehe...
<.<
>.>
Time for another App...

Oh, and it actually isn't too difficult to understand hex once you've used it long enough. I've been disassembling the TI-OS just by reading the hex and I've learned some useful things (like how to tell what model calc is being used, which areas of extra RAM are off limits, how ROM calls are handled) that kind of thing. If you happen to know which page the ROM call location is on, you can save a little speed (maybe a few hundred T-States) at the cost of a few extra bytes.

But yeah, I'm not saying it's easy, though. It makes my brain hurt, but I can get through maybe a thousand bytes of code per hour, give or take depending on how complex the routines are. That is what I had to do when I made the font hook...  ._.

You're literally reading numbers as words O.O
For some reason, that seems a little weird. Then again, so does sitting in math class reading programming books for fun, so I shouldn't be talking.
Logged
Spoiler For userbars:







Hacker-in-training!   Z80 Assembly Programmer     Axe Programmer
C++ H4X0R             Java Coder                           I <3 Python!

Perdidisti ludum     Cerebrum non habes

"We are humans first, no matter what."
"Fame is a vapor, popularity an accident, and riches take wings. Only one thing endures, and that is character."
Spoiler For Test Results:




Pages: 1 [2] 3 4   Go Up
« previous next »