#Embedded C programming

[bermondseysblog]

Unlocking the Future of Technology with Bermondsey Electronics Limited: A Leader in Embedded Software

In today's rapidly evolving tech landscape, embedded systems are at the heart of innovation, powering everything from consumer electronics to industrial machines. At the forefront of this technological revolution is Bermondsey Electronics Limited, an embedded software company that is pushing the boundaries of what's possible in the world of embedded engineering services.

Pioneering Embedded Engineering Services

Bermondsey Electronics Limited stands out as a beacon of excellence in the realm of embedded engineering services. Our team of experts specializes in developing and implementing sophisticated software solutions that are tailor-made for the unique needs of our clients. Whether it's for automotive, healthcare, aerospace, or consumer electronics, our embedded engineering services are designed to deliver reliability, efficiency, and performance.

Embedded Software Company: At the Intersection of Innovation and Reliability

As an embedded software company, Bermondsey Electronics Limited is committed to providing state-of-the-art software solutions that drive innovation while ensuring utmost reliability. Our approach combines cutting-edge technology with rigorous quality assurance processes to create embedded software that not only meets but exceeds our clients' expectations. Our dedication to excellence has established us as a trusted partner in the embedded software industry.

Mastering Embedded C Programming

Embedded C programming is the backbone of our development process. This programming language is specifically designed for the development of embedded systems and offers the flexibility and control necessary to optimize hardware performance. Our team of skilled developers leverages Embedded C programming to create highly efficient and scalable software solutions. This expertise enables us to tackle complex challenges and deliver custom solutions that perfectly align with our clients' objectives.

Why Choose Bermondsey Electronics Limited?

Choosing Bermondsey Electronics Limited means partnering with a company that is deeply committed to innovation and quality. Here are just a few reasons why we stand out:

Expertise: Our team is composed of industry veterans with extensive experience in embedded systems and software development.

Custom Solutions: We understand that each project is unique, and we pride ourselves on delivering custom solutions that are precisely tailored to meet the specific needs of our clients.

Quality Assurance: We adhere to the highest standards of quality, ensuring that our software is reliable, secure, and effective.

Cutting-edge Technology: We continuously invest in the latest technologies and development tools to ensure that our clients benefit from the most advanced solutions available.

Looking Ahead: The Future of Embedded Systems

The future of embedded systems is incredibly exciting, with advancements in IoT, AI, and machine learning paving the way for smarter, more connected devices. As an embedded software company, Bermondsey Electronics Limited is excited to be at the forefront of this technological evolution. We are continuously exploring new ways to leverage our expertise in embedded engineering services and Embedded C programming to create innovative solutions that meet the demands of tomorrow.

Partner with Us

If you're looking to bring your embedded system project to life, look no further than Bermondsey Electronics Limited. Our team is ready to help you navigate the complexities of embedded software development and turn your vision into reality. Contact us today to learn more about how we can support your project with our unparalleled embedded engineering services.

At Bermondsey Electronics Limited, we're not just developing embedded software; we're shaping the future of technology. Join us on this exciting journey and see what's possible when innovation meets expertise.

[allie-leth]

My worker firmware works! It flashed itself over, now just to add some roll back, security, and validation features. But effectively this means I never have to plug in another ESP32 to send them firmware. I can just tell them to post to MQTT from the worker firmware for logging and post the firmware binary to my local file server. This makes my life so much easier while building out this mesh of meshes multi-protocol com lib. Hell yeahhh

[0x4468c7a6a728]

i've gotta program something soon...

[i-wanna-b-yours]

SOMEONE GIVE ME A BLOODY INTERNSHIP 😭

[watchmorecinema]

Normally I just post about movies but I'm a software engineer by trade so I've got opinions on programming too.

Apparently it's a month of code or something because my dash is filled with people trying to learn Python. And that's great, because Python is a good language with a lot of support and job opportunities. I've just got some scattered thoughts that I thought I'd write down.

Python abstracts a number of useful concepts. It makes it easier to use, but it also means that if you don't understand the concepts then things might go wrong in ways you didn't expect. Memory management and pointer logic is so damn annoying, but you need to understand them. I learned these concepts by learning C++, hopefully there's an easier way these days.

Data structures and algorithms are the bread and butter of any real work (and they're pretty much all that come up in interviews) and they're language agnostic. If you don't know how to traverse a linked list, how to use recursion, what a hash map is for, etc. then you don't really know how to program. You'll pretty much never need to implement any of them from scratch, but you should know when to use them; think of them like building blocks in a Lego set.

Learning a new language is a hell of a lot easier after your first one. Going from Python to Java is mostly just syntax differences. Even "harder" languages like C++ mostly just mean more boilerplate while doing the same things. Learning a new spoken language in is hard, but learning a new programming language is generally closer to learning some new slang or a new accent. Lists in Python are called Vectors in C++, just like how french fries are called chips in London. If you know all the underlying concepts that are common to most programming languages then it's not a huge jump to a new one, at least if you're only doing all the most common stuff. (You will get tripped up by some of the minor differences though. Popping an item off of a stack in Python returns the element, but in Java it returns nothing. You have to read it with Top first. Definitely had a program fail due to that issue).

The above is not true for new paradigms. Python, C++ and Java are all iterative languages. You move to something functional like Haskell and you need a completely different way of thinking. Javascript (not in any way related to Java) has callbacks and I still don't quite have a good handle on them. Hardware languages like VHDL are all synchronous; every line of code in a program runs at the same time! That's a new way of thinking.

Python is stereotyped as a scripting language good only for glue programming or prototypes. It's excellent at those, but I've worked at a number of (successful) startups that all were Python on the backend. Python is robust enough and fast enough to be used for basically anything at this point, except maybe for embedded programming. If you do need the fastest speed possible then you can still drop in some raw C++ for the places you need it (one place I worked at had one very important piece of code in C++ because even milliseconds mattered there, but everything else was Python). The speed differences between Python and C++ are so much smaller these days that you only need them at the scale of the really big companies. It makes sense for Google to use C++ (and they use their own version of it to boot), but any company with less than 100 engineers is probably better off with Python in almost all cases. Honestly thought the best programming language is the one you like, and the one that you're good at.

Design patterns mostly don't matter. They really were only created to make up for language failures of C++; in the original design patterns book 17 of the 23 patterns were just core features of other contemporary languages like LISP. C++ was just really popular while also being kinda bad, so they were necessary. I don't think I've ever once thought about consciously using a design pattern since even before I graduated. Object oriented design is mostly in the same place. You'll use classes because it's a useful way to structure things but multiple inheritance and polymorphism and all the other terms you've learned really don't come into play too often and when they do you use the simplest possible form of them. Code should be simple and easy to understand so make it as simple as possible. As far as inheritance the most I'm willing to do is to have a class with abstract functions (i.e. classes where some functions are empty but are expected to be filled out by the child class) but even then there are usually good alternatives to this.

Related to the above: simple is best. Simple is elegant. If you solve a problem with 4000 lines of code using a bunch of esoteric data structures and language quirks, but someone else did it in 10 then I'll pick the 10. On the other hand a one liner function that requires a lot of unpacking, like a Python function with a bunch of nested lambdas, might be easier to read if you split it up a bit more. Time to read and understand the code is the most important metric, more important than runtime or memory use. You can optimize for the other two later if you have to, but simple has to prevail for the first pass otherwise it's going to be hard for other people to understand. In fact, it'll be hard for you to understand too when you come back to it 3 months later without any context.

Note that I've cut a few things for simplicity. For example: VHDL doesn't quite require every line to run at the same time, but it's still a major paradigm of the language that isn't present in most other languages.

Ok that was a lot to read. I guess I have more to say about programming than I thought. But the core ideas are: Python is pretty good, other languages don't need to be scary, learn your data structures and algorithms and above all keep your code simple and clean.

[just-my-insufferable-existance]

Should I actually make meaningful posts? Like maybe a few series of computer science related topics?

I would have to contemplate format, but I would take suggestions for topics, try and compile learning resources, subtopics to learn and practice problems

[cerulity]

frontend development is so confusing to me sdggsfgdf how can people do this for a living

i could read a thousand pages of embedded manuals and understand everything but literally anything to do with frontend development leaves me with a hydra of questions, answering one question will make me question like five other things

[spindlecrank]

Data Structures in Popular Programming Languages: A Top Down Introduction

Data structures are fundamental building blocks in programming, allowing developers to efficiently store, organize, and manipulate data. Every programming language provides built-in data structures, and developers can also create custom ones to suit specific needs. Below, we will explore: What data structures are and why they are important Common data structures in programming How to…

[emblogicsblog]

This "Project Based Training in C++ Programming" course is designed for engineering students to bridge the gap between academic knowledge and practical skills in embedded technology. The program is designed to equip students with essential industry-ready capabilities and targets the growing demand for expertise in real-world embedded systems. The course structure includes four key modules and a project module emphasizing writing optimized, high-performance code suited to software development and embedded applications.

With C++ as the primary language, students learn on a Linux platform using tools like GCC (GNU Compiler Collection), GDB (GNU Debugger), and QT for graphical applications. Each module combines foundational C++ concepts with hands-on training to ensure students can confidently tackle complex industry problems. The comprehensive project module allows students to apply their knowledge practically, honing their skills in creating efficient, optimized code tailored to embedded applications.

[bitstream24]

PiCAN FD HAT with LIN Bus for Raspberry Pi

This PiCAN FD HAT comes with a LIN Bus interface. The Microchip MCP2518FD IC provides Classical CAN and CAN FD, while a dsPIC33 microcontroller enables the LIN Bus connection. Communication to the Pi is via UART on ttyS0 using ASCII text commands. An example of the LIN-bus GUI app, written in Python3 and Tkinter, is available. It is easy to install the SocketCAN driver, and programming is supported in C or Python.

[bermondseysblog]

Embedded C Programming

Bring Products to life with Bermondsey Electronics, specialist Embedded Engineering Software Solutions & C Programming. Go to market with increased confidence.

[mtul-c]

Reading declarations with Specifiers and Qualifiers

Storage Class Specifiersauto – Can be used only within a block. A default storage class. Stored in stack.static – Either inside/outside the function. If used inside, a function, the scope of variable is preserved between function calls. If used outside a function but in a file, it the variable cannot be accessed by other file. Stored in data segment.extern – Defined in a function, used somewhere…

[machine-saint]

there was an article going around my social media elsewhere that was talking about how programming language design needs feminism. i think there are good notes in the article about English-centricism, and i can't speak as to whether or not the problems the paper identifies (emphasis on formal theory over "is this pleasant to use") are actually a problem, but i was struck by this quote (in the paper embedded at the bottom)

The current standards of evaluation in the PL community are set from a masculine perspective as well, valuing formalism and formal methods over user studies, quantitative over qualitative work, and the examining of technical aspects over context and people.

because... i had previously seen people argue that the "C is good enough, just don't write bad code lmao" attitude that you see a lot of the time is also masculine, because it's very individualist and "the compiler should get out of my way" type thinking. this came to a head recently with the whole Rust-in-the-kernel thing.

so we have a situation where in one case, formalism is masculine. in another, lack of formalism is masculine. and i think this is my problem with a lot of this sort of feminist stuff: it makes these big sweeping statements about how such-and-such behavior is masculine and doesn't consider cases where the opposite is also masculine.

i think the paper also oversteps by effectively using "feminism" to mean "ask[ing] why things are the way they are, and by that [examining] how we can make them more fair", regardless of whether or not gender has anything to do with it. so "feminism" sort of gets scope-crept in a way that i don't think is conducive; if i were to advocate for installing a wheelchair ramp or a curb cut, this is now feminism.

don't take this as a referendum on All Of Feminism, i'm just annoyed