General > General Technical Chat
ASM programming is FASCINATING!
<< < (7/24) > >>
KL27x:
To the OP, here's a thread that touches on many specifics of PIC ASM. Some gotcha's, some IDE tricks, some general considerations for actually writing assembly for 8 bit PIC microcontrollers. It's easy reading and might provide some insight.

https://www.eevblog.com/forum/beginners/assembly-code-help!-pic16f57/msg1857261/#msg1857261

BTW, I'm pretty sure I basically fixed the bug. But the last code change I made, like any good scientist I changed two things at once. If the guy just undoes one of those things, I bet the bug is fixed. In my defense, I had real, important work on a short timeline fall in my lap at that time. And I also completely lose interest in the final details once I know I can do it. If he had gifted me a machine, now that would have been different. :)
tggzzz:

--- Quote from: VK3DRB on July 29, 2020, 01:54:01 am ---No one has ever written anything in assembler. But they have used an assembler and written code in assembly language. There is a big difference between an assembler and assembly language. Notepad++ now call it "Assembly" because I advised the authors several years ago they had the terminology wrong. They agreed. (Notepad++ --> Language --> A --> Assembly).

--- End quote ---

I'm not entirely sure what you mean, but what do you think I wrote in for my first computer? The total memory available to me in my house and at college was 128bytes.

Yes, bytes.
tggzzz:

--- Quote from: MK14 on July 29, 2020, 01:51:30 am ---
--- Quote from: joeqsmith on July 29, 2020, 12:40:34 am ---Don't.

--- End quote ---

But, doing at least some assembly language. Can be fun and educational. Even a few hours at it, can be rather educational and fun. Even if that is the first and last, short assembly language program you ever end up writing.

--- End quote ---

Being able to read assembly is extremely useful when doing embedded programming, and having to work out what the compiler+hardware is actually doing!

Ditto optimising the shit out of inner loops.

Ditto assuring yourself that the multicore code has the necessary memory barriers.

Plus I've used it as the basis for interview questions along the lines of "outline in pseudocode the instructions generated for a C function call".
KL27x:
Just semantics. An assembler is analagous to a compiler. You wrote programs in assembly. The assembler turned that into machine op codes. Even if you wrote in machine code, you still didn't write in assembler/compiler.
MK14:

--- Quote from: KL27x on July 29, 2020, 08:06:26 am ---Just semantics. An assembler is analagous to a compiler. You wrote programs in assembly. The assembler turned that into machine op codes. Even if you wrote in machine code, you still didn't write in assembler/compiler.

--- End quote ---

As well as calling it, "I just wrote an assembly program", people also in practice seem to say "I wrote it in assembler".

But people never seem to say "I wrote it in compiler".

Similarly, paper, when printed, is then called a newspaper.
But you might say to someone, (when you want the newspaper) "please hand me the paper", or "Please go and fetch the paper".
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod