| General > General Technical Chat |
| ASM programming is FASCINATING! |
| << < (9/24) > >> |
| Ian.M:
--- Quote from: KL27x on July 29, 2020, 06:56:41 am ---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. :) --- End quote --- @KT27x: Fixed the link for you. @all, I was an interested bystander and limited participant in that thread. IIRC It was an exercise in patching the worst spaghetti code that has been seen here in many years on a deeply unfavourable architecture. IMHO Assembly language programming of complex projects on the baseline (12 bit) PIC core risks brain damage to all participating sapient lifeforms vulnerable to impact trauma, and not capable of directed autistic savant hyperfocus. :scared: For your own safety, please use adequate PPE (e.g. boxing helmet and thick padding on desk and cubicle walls |O ), and have your significant other on standby with a tranquilliser, straitjacket and your preferred choice of sedatives. :popcorn: If you engage in rubber duck debugging, you will find that the ducks are a consumable resource! :horse: The classic and extended midrange (14 bit) PIC cores are much less trauma inducing, and can actually be satisfying to code for (in a hair-shirt ascetic sort of way). TLDR: If the second group of numbers in a PIC12 or PIC16 part number begins with a '5', run screaming for the hills! |
| ebastler:
--- Quote from: KL27x on July 29, 2020, 09:08:06 am ---I have yet to hear anyone recompile their assembler. That might bug me. --- End quote --- Yep, me too. On a loosely related note: Is there a commonly accepted term for the process of translating VHDL or Verilog into an FPGA configuration binary? "I synthesized, mapped, placed & routed it" is a bit long. ::) |
| Ian.M:
"I built the binary from the ....." or is that over-simplistic? |
| mfro:
--- Quote from: ebastler on July 29, 2020, 10:42:29 am --- --- Quote from: KL27x on July 29, 2020, 09:08:06 am ---I have yet to hear anyone recompile their assembler. That might bug me. --- End quote --- Yep, me too. On a loosely related note: Is there a commonly accepted term for the process of translating VHDL or Verilog into an FPGA configuration binary? "I synthesized, mapped, placed & routed it" is a bit long. ::) --- End quote --- Recompiling my assembler regularly - with every binutils upgrade. |
| joeqsmith:
I took a class where we used an old computer using machine code. You found yourself memorizing the hex codes for the instructions. There was no debugger so you would enter your code and just see if it worked. There was no way to store your program and you had to key it in everytime you worked on it. The first time I used an assember was after taking that class. I'm not sure if the punch cards were any better.... |
| Navigation |
| Message Index |
| Next page |
| Previous page |