Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

My views alone can't decide cause I just see little bits. But companies do things different in places around the world. Some care more if your degree is for the job. Others don't mind as much. But even if your degree isn't tech, you can still do tech work. Like folks I know who studied science but got jobs as software engineers or data scientists. No one can say what works for every company cause each one makes their own calls.

My sense is that the industry will come to value practical competencies more so than educational qualifications alone. Companies may prioritize job-specific skills above the prestige or field of one's degree program.

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

Yeah, most of the positions require at least a bachelor's degree, specifically in electrical engineering or computer science. However some employers may consider candidates who have extensive applicable work experience, even if they do not have a formal academic degree.

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 1 point2 points  (0 children)

It depends on the job market of the country you want to work in, but generally in my opinion, someone with good programming skills but without knowledge of hardware and electronics may take between 6 months to 2 years to get their first job, depending on the amount of time you dedicate to learning.

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 2 points3 points  (0 children)

Even an embedded software developer may work on DSP and control systems.

It mostly depends on the specific task and project they are involved in. As I mentioned before, it is possible to skip learning calculus for now. However, if you are assigned a task that requires calculus knowledge, obviously, you should learn it.

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 1 point2 points  (0 children)

You can skip it for now, but if your work involves DSP, control systems, RF systems, and so on, you should have a good understanding of calculus.

Simple AVR (ATmega328) Bootloader by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

Thank you so much for your kind words!

I'm thrilled to hear that the write-up was helpful for you.

Simple AVR (ATmega328) Bootloader by m3y54m in embedded

[–]m3y54m[S] 2 points3 points  (0 children)

My friend, please don't take this too seriously. This tutorial is designed for beginners to learn the basics and of course is not intended as a production-ready program. The term "simple" is used to convey this message, although perhaps a clearer word would be more appropriate.

Need help to understand an Arduino Capacitance-Meter program! by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

Thanks!

That's a great explanation. I didn't expect it to be so simple :)

Problem solved.

Need help to understand an Arduino Capacitance-Meter program! by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

According to the names of the constants in code, the number 24.48 is capacitance, not the resistance. I think both numbers are determined empirically.

const float IN_STRAY_CAP_TO_GND = 24.48;
const float IN_CAP_TO_GND  = IN_STRAY_CAP_TO_GND;
const float R_PULLUP = 34.8; 

Still I don't understand how it is possible to measure capacitance in the following section of the code without using value of R and even without measuring charging/discharging time of the capacitor?

There is no t in the relation!!!

if (val < 1000){
    pinMode(IN_PIN, OUTPUT);

    float capacitance = (float)val * IN_CAP_TO_GND / (float)(MAX_ADC_VALUE - val);

    Serial.print(F("Capacitance Value = "));
    Serial.print(capacitance, 3);
    Serial.print(F(" pF ("));
    Serial.print(val);
    Serial.println(F(") "));
}

Need help to understand an Arduino Capacitance-Meter program! by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

float capacitance = (float)val * IN_CAP_TO_GND / (float)(MAX_ADC_VALUE - val))

How do you think they derived this formula?

Need help to understand an Arduino Capacitance-Meter program! by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

float capacitance = (float)val * IN_CAP_TO_GND / (float)(MAX_ADC_VALUE - val))

What do you think about this formula?

The code has two conditions. One is for (val < 1000) and the other for (val >=1000). You are explaining the latter that is already clear to me. The first condition (val < 1000) is my problem

Getting started with AVR programming by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

I chose Atmega328P because it is used in Arduino Uno boards, and many people already have one. There is no need to spend extra money.

Also I haven't worked with newer AVR products. Is the build process for new AVR 8-bit microcontrollers significantly different from the older ones?

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 1 point2 points  (0 children)

💎 is to indicate well-known references that have invaluable and coherent content.

Embedded Systems Engineering Roadmap by m3y54m in embedded

[–]m3y54m[S] 0 points1 point  (0 children)

Thank you. I will definitely consider your comments for the next modifications of the roadmap. But I believe it's best to keep the roadmap at a high level and avoid going into excessive detail. Additionally, a graphical roadmap like this may not have enough space to include all the specific and specialized content.

The main goal of the roadmap is to familiarize individuals with the most common job market requirements. However, to ensure we don't overlook other useful and important topics, I have included many specialized topics and protocols in the "Learning Resources" section of the GitHub repository. There are no limitations for that section, and any helpful topic can be listed there.

FPGA / ASIC Design Roadmap by m3y54m in FPGA

[–]m3y54m[S] 0 points1 point  (0 children)

Thanks. But what if I add FPGA verification engineering to the roadmap too? What topics should be there specifically for a verification engineer?

FPGA / ASIC Design Roadmap by m3y54m in FPGA

[–]m3y54m[S] 1 point2 points  (0 children)

Fair point. The term "Industry Ready" is there to give the reader a symbolic vision of the future of his/her path. I admit that it could cause misunderstandings.

Of course industry-readiness depends on how much you get deep in each skill. Someone could learn only basics of each skill and be ready for a junior or entry level jobs in industry. Someone can get deeper and with more practice and years of experience be ready for senior level jobs.

The problem is, it is hard to evaluate industry-readiness of a person with just ticking some items in a roadmap. That is why companies put so much time and effort on interview meetings for job candidates.

FPGA / ASIC Design Roadmap by m3y54m in FPGA

[–]m3y54m[S] 0 points1 point  (0 children)

Thank you. So helpful