I followed Ben Eater's series originally and bought the components to start with. I had already done some Arduino and had basic supplies so when I got frustrated with doing this on a breadboard (likely not the best quality) and the wires flying out as things got more complicated I wanted to get on ...

vasm 1.9e has been released, it has the fix for this issue that was in the daily source snapshot.

Well, now I’m diving down a rabbit hole from searches based on the elided.

Thanks!

The programming language Common Lisp has "signed-byte" and "unsigned-byte" types which can be parameterized by the number of bits involved, and has a "byte" function for specifying a consecutive run of bits within a larger integer for various shift/mask operations, and it inherits this from ...

"Octet" in French (and maybe other languages too) is a byte.

Even English, maybe. :D

*mumbles something incoherent about practically all of the RFCs he’s ever read* ;)

Edited to add an aside: way back, ‘byte’ used to be used like ‘word’ in the sense that it was a machine-specific size. As an ...

Tried your fix out this evening; works just fine here!

Nice! Thank you for trying.

Just in case anyone wants a fix before they do a new release and doesn't want to run on a daily source, my final change (which is really going to end up being the same as the first in the actual binary, due to ...

I was going to post a patch after testing a few things and deciding how I'd fix it - but I decided to check first ->

It looks like they've actually already fixed if if you download their daily source instead of the released source.

The change I decided to finalize on does it it slightly ...

output_ihex.c

It buffers the character and then increments a file-local (declared static outside any function - so "global" for any code in the file but not actually exported) addr value.

When it actually outputs, it does the check - checking against that addr value in write_data_record() - but ...

It seems like it's adding 1 to both segment reports. "seg8000" is only 3 bytes long, not 4.

I had the thought that this could be 'the segment report is reporting start (inclusive) to end (exclusive)' - but I haven't managed to find any docs on the wide output format, yet, so who knows.

I had ...

I'd bet that a larger proportion of the people who landed here via Ben Eater videos are using or have used vasm at least a little bit.

I also currently see this as 'probably a bug in the ihex module', and I also don't grok at all why the address size options are what they are, but I'm sure it makes ...

I think I've been nerd sniped. The docs say


‘-i8hex’
Selects a format supporting 16-bit address space (default).

‘-i16hex’
Selects a format supporting 20-bit address space.

‘-i32hex’
Selects a format supporting 32-bit address space.


I got this by giving it -i16hex, and by the description of ...

Possible bug in the intel hex module?

I'd need to read the docs of that module carefully but it definitely looks like some behavior of that module, bug or not:

using this code:

.org $8000

start:
jmp start

.org $FFFA
word start
word start
word start



Look at the .lst output ...

I pulled the data sheets for the actual parts I received in my kit to the best of my ability.

I am not going to use pin names from the datasheet for a different part when I am quoting portions of the datasheet for my actual part and those portions actually refer to the new names. Which is what I ...

The one I uploaded was a fresh copy from TI.

I’m pretty sure I grok approximately what’s what now.

I searched exactly my part number, and landed on the ti page for the 2016 datasheet, which lists exactly my part number in the table inside the sheet.

I’m not going to say I know exactly what you ...

According to the PHP manual and the Programming PHP O’Reilly book, the only datum embedded in a PHP session cookie is the PHP session ID. As a session can be started before a user has actually been authenticated, the presence of the session cookie in itself is not an indication that a user has ...