#Assembly Language

[zipp-os-official]

Starting Production🎉🥂

ZippOS is an alternate operating system for stand alone “spacial computing” devices. The goal of this project is to provide end users, who at their own discression, void their warranties to replace pre-packaged software bundled with their hardware. As the lead developer of ZippOS, and as an end user of a “spacial computer”, I am displeased with the current operating software, and the decisions of parent companies that distribute these products are inheriently unstable, brown-nosing share holders and consumers, and completely unaligned with the end users. As these devices are marketed as computers, I want to provide software for said computers as a choice for the end-users who feel the same as I do.

ZippOS will be a lighter(get it?), faster booting operating system built from scratch with Rust-Lang and some ARM/RISC-V assembly code to replace both the BIOS (ZIOS) and the operating system. The operating system’s goal is to have the same user functionality and multimedia multi-instancing in a mixed reality setting, citing BeOS/HaikuOS as inspiration. This operating system will have security and graceful degradation as the main focus for user safety because the main enemy for ZippOS is the companies who made the stock software it replaces on the end-user’s spacial computer. Users can also enjoy various stimulating options for navigating the software (i.e. “rolodex” style hub menus, table-top program/application storefront, “grabbing” and “throwing” programs/screens to be cast/mirrored to and from realspace and cyberspace, etc). ZippOS is a project software operating system under development, and currently has no plans to publicly publish to the open net, nor are there any current plans to open-source the software.

[wordacrosstime]

Programming Embedded Systems (with C and GNU Development Tools)

[Programming Embedded Systems (with C and GNU Development Tools). By Michael Barr & Anthony J Massa. 2nd Edition, 1 October 2006. Publisher: O'Reilly Media. Paperback: 301 pages, Dimensions: ‎ 17.78 x 1.98 x 23.34 cm. ISBN: 978-0-596-00983-0]

In the past 15 months or so I elected to expand my personal and professional skill set to include working with small computing systems, sometimes referred to as microcontrollers.  These devices have become virtually omnipresent, in everything from automobiles and bar-code scanners to toasters and doorbells.  If you operate a late-model vehicle, for instance, you may have as many as 70 (!) of these devices in the car controlling everything from the fuel mixture to emissions to anti-lock brakes and collision avoidance sensing.

I was interested in moving into this arena as part of my career, as there were many openings for people with a strong understanding of the imperatives attendant on both the software and hardware of embedded systems.  I knew a bit about the electronics side of things and I have done software development of one sort or another most of my 40+ years as a professional, but this arena poses unique challenges and opportunities.  I knew I needed to do some specialized self-teaching, and this book seemed like a great place to start.

To start with, what exactly is an embedded system?

As the name implies, it is a system - in this case a miniature computing device - that is a component of a larger framework.  This larger framework can take on myriad forms.  Some of the largest such frameworks are satellite networks.  The embedded system comprises hardware - a central processing unit, or CPU, along with some (minimal) on-board memory and one or more electrical interfaces (e.g. a USB or RJ45 jack) through which it can communicate with the outside world. 

Unlike the computers most of us are familiar with, such as Windows or MacOS-based laptops or Linux servers, these devices often do not have an operating system (WIndows, MacOS and Linux are all operating systems) that performs many of the low-level functions needed to keep the device running and useful. 

This keeps the device flexible in terms of how it can be used, but at the expense of more detailed and subtle development and maintenance requirements.  Thus, the "software" on an embedded system may be a very small bit of computer code that simply turns on the interfaces electrically and then waits for something to happen.

Programming software for these systems is intriguing but fraught with issues that an ordinary computer user never sees.

For example, given that the memory and interface resources on these devices tend to be rather modest, it's necessary for the programmer to take care of any bookkeeping that is necessary to keep the basic functions from colliding.  If one of the interfaces is used to provide a scanned barcode to a waiting receiver, it must pass that information through some on-board memory first.

The embedded software designer needs to be sure that this information can't be corrupted, or "clobbered", by a competing task that might be, for instance, putting the scanning laser into sleep mode to save power.  Moreover, there are cases where the same locations in memory need to be shared by tasks as a part of getting work done.

But what happens if one task is trying to write data to a specific memory location while another task is trying to read from it?  Is there always a specific order in which this happens?  What happens if either operation is incomplete for some reason?  Will the device recover and continue to operate, or will it lock up?  The aforementioned are but a tiny set of examples that the developer must bear in mind.

Messrs Barr and Massa have many decades of experience between the two of them in just these kinds of environments. I was delighted to see just how easy this book is to read and how thoroughly they cover all of the issues that accompany such a software development enterprise.  They are careful to create and explain examples that use commonly-available development kits (I use an STM32 ARM Cortex-M Development Board myself; there is a photo of one such system below) and free or nearly-free software tools to break down the barriers to entry in this field.

This book is really as much about operating system design as it is about microcontroller software development; if one is interested in what nearly every operating system must do, this volume talks all about it. 

Above and beyond this, it is a wealth of anecdotes, sample code, and general wisdom that will really ease the novice into this exciting world of programming and small-device control.

I highly recommend it to anyone who wants to get down on the bare metal with computers.  It is necessary to be at least familiar with the C programming language (almost all of the examples are coded in C) and it would be very helpful to have worked with at least one Assembly language as well.  Beyond that, the only requirement for getting the most out of the book is a willingness to experiment and be delighted.

Image Credits (from above down; with thanks to copyright owners): (1) STM32 ARM Cortex-M Development Board © Copyright Owner, date unknown (2) Book Cover © O'Reilly Media 11 October 2006 (3) Michael Barr © Barr Group 2012-2025. (Anthony J Massa, no photograph found)

Kevin Gillette

Words Across Time

4 February 2025

wordsacrosstime

[programmingassignmenthelperbd]

"Save this & read Caption for details!

For take our services contact with us Whatsapp/Telegram:+8801772432396 Email 1:academiccourseworkservices@gmail.com Email 2:programmingassignmentsservices@gmail.com

we provide all type of academic services.such as: 🟩PHP 🟩Python 🟩C 🟩C++ 🟩Java 🟩C# 🟩Visual Basic .NET 🟩JavaScript 🟩SQL 🟩Assembly language 🟩R 🟩Go 🟩Classic Visual Basic 🟩MATLAB 🟩Swift 🟩Delphi/Object Pascal 🟩Ruby 🟩Perl 🟩Objective-C 🟩Rust 🟩Scratch 🟩SAS 🟩Kotlin 🟩Julia 🟩Lua 🟩Fortran 🟩COBOL 🟩Lisp 🟩(Visual) FoxPro 🟩Ada 🟩Dart 🟩Scala 🟩Prolog 🟩D 🟩PL/SQL 🟩Bash 🟩Powershell 🟩Haskell 🟩Logo 🟩Transact SQL

📌 Save this and Share with others!

View this post on Instagram

A post shared by ProgrammingAssignmentHelperBd (@programmingassignmenthelperbd)

[gobusto]

on a related note, fans of Doing Everything In Assembly™ might be interested to know about MenuetOS:

MenuetOS is an operating system with a monolithic preemptive, real-time kernel written in FASM assembly language ... It runs on 64-bit and 32-bit x86 architecture computers.

never ceases to blow my mind that Roller Coaster Tycoon was written in fucking Assembly. you mean to tell me one singular guy wrote a whole damn videoed game like that in Assembly?? I thought only a C++ compiler could do that

[revalition]

thinking about how caustic is used in disco elysium to refer almost exclusively to loss. loss of love, loss of the self, loss of the world...

[oxymoronicdumbass]

“trans culture is wearing baggy clothes”

“trans culture is liking spider-man”

nuh uh to be trans is to be your own pallbearer to carry the weight of a dead person around with you my gender can’t speak but even if it could it’d stay hidden in the corner of every room trying to keep quiet anyway learn to piece my parts together on-

[silicon-tmblr]

Oh yeah, guess I should mention what put me on hiatus ahaha — Aside from regular burnout, I was also busy working on a mod for Stardew Valley these past few months!

After playing Stardew Valley for a while, you might've gotten married and wound up having or adopting children with your spouse... in which case, you would've ended up with two kids who never grow past the toddler stage and run about the house aimlessly. Well...

Growing Valley - Child NPCs lets those funky untalkative toddlers that wander your home grow up into fully-fledged NPCs!

More details under the cut! (or you could visit the mod page for even more details ahaha)

This mod comes with six unique kids designed in appearance and personality to resemble six of the vanilla marriage candidates! There's also customizable kids to fill in for remaining situations, whether because you've married a modded spouse, or because your spouse of choice hasn't gotten a unique kid yet.

So far, Alex, Leah, Penny, Sebastian, Elliott, and Emily have gotten unique kids designed after them, but any child can be manually selected through the config to show up in place of the defaults.

Customizable kids!

Questionably dishonest antics!

Young ma'am, that's not edible (or potable)!

Aside from being goofy little buggers who want to drink dye (well only Emily's daughter would try that... right?), they'll also wander around town, chat with you, and accept gifts like any other character. Winter outfits were recently added too, so look forward to seeing them bundle up for the cold!

---

On a more personal note, I've been real happy to be able to return to pixel art; it's how I started out as an artist, so getting to flex exercise the skills I've developed since those early days has been a delightful opportunity!

Now I'm sick of doing it though so I need to take a hiatus from this and return from my hiatuses elsewhere ahaha

[ailurinae]

TY!

Not to defend implicit operand sizes but a defense of AT&T syntax I truly don't get is that it not having implicit sizes is good and makes for better code like look if you're writing like, 8086 and you say

mov ax,bx

obviously it's going to be a word? There's no other size it could be?

in general you're not going to have a lot of mixups regarding operand size its not a huge concern...

[nell0-0]

Would 10/10 have time to draw and write if I just stopped assembling(?) furniture and moving heavy stuff around. Would not recommend either, there's an option to pay for people to do it for you. Which sounds super nice. Then again, I'm broke (spent all the money on the furniture pieces), so there I go again.

[programmingassignmenthelperbd]

"Save this & read Caption for details!

For take our services contact with us Whatsapp/Telegram:+8801772432396 Email 1:academiccourseworkservices@gmail.com Email 2:programmingassignmentsservices@gmail.com

we provide all type of academic services.such as: 🟩PHP 🟩Python 🟩C 🟩C++ 🟩Java 🟩C# 🟩Visual Basic .NET 🟩JavaScript 🟩SQL 🟩Assembly language 🟩R 🟩Go 🟩Classic Visual Basic 🟩MATLAB 🟩Swift 🟩Delphi/Object Pascal 🟩Ruby 🟩Perl 🟩Objective-C 🟩Rust 🟩Scratch 🟩SAS 🟩Kotlin 🟩Julia 🟩Lua 🟩Fortran 🟩COBOL 🟩Lisp 🟩(Visual) FoxPro 🟩Ada 🟩Dart 🟩Scala 🟩Prolog 🟩D 🟩PL/SQL 🟩Bash 🟩Powershell 🟩Haskell 🟩Logo 🟩Transact SQL

📌 Save this and Share with others!

View this post on Instagram

A post shared by ProgrammingAssignmentHelperBd (@programmingassignmenthelperbd)

[e-adlirez]

Quick question non-English Stilton fandom

So you know Karate Mouse? The one where G has to participate in a karate tournament and do a 2005 Michelle Khare black belt speedrun in the process? In the book the third placer is a Filipino; what was his name in your version? If you're gonna let me know, lemme know what language you read that book in. Thanks ^^

Italian, Catalan, and Dutch translations below:

-

Italian: Hai presente Iena? Il figo per il quale Geronimo é costretto a partecipare al Camponiato Mondiale di Karate e fare una speedrun da cintura nera manco fosse Michelle Khare nel 2005? Nel libro (Te Lo Do Io Karate), il karateka che si piazza al terzo posto é di origine filippina. Come viene chiamata nella versione italiana (io ho solo quella inglese)? In caso non hai la versione italiana, sono curiosa di sapere in quale lingua possiedi il libro. Grazie mille ^^

-

Catalan: Conocen "No volies karate, Stilton?"? El libro en el que Geronimo tiene que participar en un torneo de karate y mientras hacer un 2005 Michelle Khare cinturón negro speed run? En el libro el ganador de tercer lugar es Filipino; cuál es su nombre en tu versión? Si me van a decir, pls díganme en que lenguaje leyeron ese libro. Gracias ^^

-

Dutch: Kennen jullie karatemuis? Dat boek waarin G meedoet met een karate wedstrijd en een 2005 Michelle Khare zwarte band speedrun doet? In dat boek is de derde plaats winnaar Filipino; wat was zijn naam in jouw versie? Zeg me alsjeblieft in welke taal je het boek hebt gelezen, mocht je antwoord willen geven. Bedankt ^^

[haveyoulistenedtothisalbum-poll]

Tracklist:

bission mriefing • gadget • chang'e • attract mode • floppy disco • character select • scph-1001 • n.a.o.m.i. • like a reactor • context • assembly

Bandcamp ♪ YouTube

[trickstersaint]

hey hi hello! first of all i'd like to say i took your patron saint uquiz and it. Changed my life unironically it's so good. i follow you now because every line in that quiz was a gut punch and i loved it. top tier hurt honestly

my question is this - i am a fanauthor. on the side i also write my own original fiction but i specialize in fanfic. Am I allowed to use your poetry for a reference folder? I wouldn't use your poetry in a fic without explicit permission and without linking back here of course, and I'd never use it for commercial work outside of maybe taking inspiration without copying, but I wanna have a ref folder of Things That Made Me Feel Things about a character. It's not planned to be public as of yet, it's just supposed to be a bunch of screenshots in my drafts, but I'd like to maybe one day make it public once the fic was complete. (I already have your blog linked in my drafts actually, so if it goes public I'm not gonna forget.) I just want to make sure you're comfortable with me using your poetry for fanfic of all things

It's cool if not and have a great day! I still think your poetry is great and evocative and all

hi, anon! you're all good, i prommy. so glad you like the quiz + the poetry, and i would always prefer people come and ask questions if they're uncertain! no trouble at all.

my general stance is that as long as it's clearly credited, i am totally cool with my work being used in personal projects. like you said, i've got a tag for the things that people make! i love to see what people create. if it's for a noncommercial creative project then i would say there's no need to ask beforehand (unless it would make you more comfortable to ask, in which case go ahead and i'll almost certainly say yes <3). my only thing is that if you post it, please tag me in it/send it to me so that i can reblog it here for people to see!

if there are any questions about using my work that anyone has, feel free to ask. i don't think i've got anything particular going on outside of common practice! same way you'd treat, like, a richard siken poem or smth: you wanna credit it so that people can find the source material, and make sure you're not using it for profit unless you have an understanding with that author. i trust you all to be decent about it <3 kiss kiss go out and make your cool little things so that i can be delighted and amazed with them

[assembly-official]

Assembly is not enough, i need to fuck my processor

VHDL or Verilog. I don't have any experience in Verilog, but have made some simple stuff on FPGAs with VHDL; it's pretty cool, but also quite frustrating since it's simultaneously the lowest level programming you'll probably ever do (as it is changing real hardware), but it's also quite abstract, so you don't really know what the compiler does; this makes fixing (heisen) bugs real tricky.

If you ment 'fuck my processor' more literally I recommend something with a LGA socket, because you will bend the pins of a PGA CPU. Also dry it off before reinserting it in your motherboard. I don't know how you'll get any real pleasure from it, but feel free to try!

[randomstuffjustrandom]

Language

Steve: *says a “bad language word” * All the avengers: LANGUAGE!!! Steve: seriously you told everyone???!!!! That was years ago!!! Bucky: sorry punk. Like you said… it just slipped out *smirks* Steve: oh come on

[athenov]

i hate duolingo so much its unreal