Embedded Development Board

What are the advantages and disadvantages of Embedded development Board ?

I don't think it you can simply say that Embedded development Board's have advantages and/or disadvantages. For the most part, they are very advantageous tools that a student or an engineer can use to learn about microprocessors. Whether it be an introduction to the topic or for hobbyists, even up to industry level prototyping or experimentation for engineers.

The dev board creates an easy to learn platform that already includes components for interfacing, input/output, a power circuit, and other peripherals depending on how advanced of a product you are using.

Ofcourse they aren't perfect, and will have limitations, but I wouldn't call it a 'disadvantage', it would just be a limitation of that certain product, and you could always look for something that can offer what you're looking for. Again, 'Development Boards' is a very broad term that encompasses a number of products.

I think a better question would be, "What are the advantages/disadvantages of [insert name of product] dev board?"

You might find this useful:
"What development board to use? (Link)":http://hackaday.com/2011/02/01/what-development-board-to-use/

I have used embedded development boards in prototype products. They allowed me to test the system as a whole, before committing myself to a final design. The final design then used the processor and a few of the peripheral chips on a custom pcb.
So would you say that there were advantages or disadvantages in the situation, no, they serve a useful purpose, no more, no less,
cheers,
Richard

h2. Advantages of embedded

* Small size and faster to load
* More specific to one task
* Easy to manage
* Low cost
* Spend less resources.

These operating system is dedicated to one device so performance is good and use less resources like memory and micro-processors

h2. Disadvantages of embedded

* Difficult to upgrade
* If any problem occurs then you need to reset settings
* Nearly not scalable
* Hardware is limited
* Troubleshooting is difficult
* Difficult to transfer data from one system to other


https://www.sagipl.com/embedded-development/

Hi,

One aspect i have not seen a lot of examples on, is the upgrade of software for an embedded device.

An example, would be that if you created a product for the home, and wanted to upgrade that product with new features, or revised code, what are the best approaches to upgrade the embedded system. Is it Ethernet with USB fallback, or RS232 fallback. What mitigations can be implemented should one route to upgrade fail etc.

Are there any resources for design guidance on remote upgrades - since this aspect does not seem to be covered by the texts or development systems i have used.

Thanks and regards,

Richard.