c programing next?

hi,
i want to study embedded systems,
i leaned c programing, what is next, and all steps next?

The best way to go is to decide on a problem you want to work on or an embedded app, etc.
For example maybe you would like to create your own weather station. So now you begin looking for the embedded board that will let you do that easily and cheaply (or whatever budget). What data do you want to collect? Maybe start with temperature and humidity. Then later add windspeed and direction. Etc.

Best to go with something you are interested in. Maybe you'd like to create a caching web proxy for a single-board computer.

thanks Rinndalir,
i learned php, mysql, c, linux, networking
i dont know any thing about embedded systems, how to begin embedded systems? what are the steps?
i made some searches on google but i want the steps, please help me
i want to make something like programing wireless for airplane

Hi,

You could start by looking at: https://www.raspberrypi.org/ to see some of the projects.

https://www.raspberrypi.org/magpi/ is the Rpi magazine with loads of information.

ARM Wiki can provide some useful information & links to help you.

EDIT: Please consider looking at: http://www.linuxquestions.org/questi...#faq_lqwelcome to help you when composing questions/posts/queries.

Hope this helps.
Have fun & enjoy!

Originally Posted by a22an i want to make something like programing wireless for airplane

You want to do a remote control airplane? RC airplane?

Originally Posted by Rinndalir You want to do a remote control airplane? RC airplane?

no, i will start with a small thing now
thanks all

Originally Posted by a22an no, i will start with a small thing now thanks all

Some consider single-board computer as embedded and maybe you do too. You can learn some stuff related to embedded using them but really if you want to try embedded stuff we're talking breadboards and atmel and things like that. These can be low cost too and if you make a mistake it is low cost.

Originally Posted by a22an hi, i want to study embedded systems, i leaned c programing, what is next, and all steps next?

Very broad question. Embedded is not just a one-of topic.

Part of what I can say is the movie line from my signature, "Never give up, never surrender!" Be persistent, be inventive, learn to approach problems from various directions and do not give up until you explicitly can explain everything.

Recalling when I first started we had a front panel which was dependent on a low speed serial interface. Occasionally the front panel would get screwy and then clear up after a second or two, which was the refresh rate. The two engineers responsible bantered, one claimed that it was the serial connection, the clock rate .... yeah a whopping 1200 baud! ... was not correct and thus slipped from time to time and that this was the problem. The other person claimed it was the screen task which was corrupting the received data by writing new data to the buffer which was currently being loaded to the screen and thus the data being written was a mixture of two screens of data. It was a little bit of the second iteration. The receive buffer was circular and contained old data, but the screen allowed 15 characters whereas the engineers tend to choose multiples of 2, therefore the screen buffer was 512 bytes in length. At the time of wrap-around the logic to take care of this was not too well written and as a result, it wrote in three chunks, ending bytes + some junk, some junk + starting bytes, the resolved buffer. And thus it took 2 seconds because you'd catch one fragment either the beginning corruption or the ending corruption and then you'd get the corrected result. The other issue was that we'd see meaningful data, just out of place because the 15 characters per screen meant that as the buffer wrap occurred, we'd hit it at different points in old screens of data. Convenient actually because if we hit it exactly, we might have seen something like "Setting Value=15" and say the "=15" was corrupted exactly with "=01", we'd have had a harder time detecting and debugging it. Instead we'd see something like "Setting VataRate" and then it would clear up. So that might be something like a former screen showing something like "DataRate=15" and at the wrap-around we had grabbed the "taRate" thus overwriting what we intended to see, and once the copy function caught up we'd get the intended data.

The dual issue there was that it had been a months old problem, people had moved ahead to deal with other parts of the product, and everyone made assumptions which they didn't take any time to verify or even correct. In this case it was a contained corruption of data, but it it were not it could've been a much larger system stability issue.

So my (sorry, lengthy) lesson is to not ignore the trivial, not overlook something just because you assume you understand the problem and evaluate it to be trivial, it may not be.