Explore >> Select a destination
|
You are here 
|
embeddedartistry.com | ||
| | | | |
embedded.fm
|
|
| | | | | You need to write your first program for an embedded system. Your IT people say that you can have any software you need as long as it is Microsoft Office. Do you have everything you need to do your job? No, you're in big trouble. Embedded systems programming uses a set of very specialized tools, and if you've never used them before, you can spend a lot of money and not get what you need. This week on Embedded Wednesdays, we look at the tools used to produce embedded systems firmware. We give an overview of the compilers, debuggers, and IDEs you will be using. After reading this post, and doing some research, you should have the information you need to go to your boss and say "NO, I can't control that cutting laser with an Excel macro. I need this..." | |
| | | | |
jborza.com
|
|
| | | | | Closer to the machine I started my way with programming with Microsoft QBASIC on DOS, I did try (and succeed) to copy code for a game from a BASIC book, and it did run, but I didnt really get development back then. I didnt really understand how and why it works, and most importantly, how to write my own code to implement a different game. Later I was playing higher level languages such as Pascal and C in the high school and PHP at home. | |
| | | | |
opguides.info
|
|
| | | | | Chapter 10.5 - Leaning Two Languages At Once # Back in the Into The Hardware section we looked at some of the inner workings of the CPU, and briefly looked into how the CPU only understands machine code, 1s and 0s that make up individual instructions. Now, theres absolutely no reason to ever think at that low of a level, the lowest you should ever care to look at, as mentioned there, is assembly. | |
| | | | |
rust-lang.github.io
|
|
| | | |||
