How in practice is the transfer of Arduino projects to a separate device?

Question

Arduino

I just started to study the interesting field of developing devices on Arduino, and immediately asked for the future - how then to repeat my achievements without the participation of the Arduino Uno control board? The question is probably stupid, but please treat the newbie with understanding. I only believe that the program should be transferred to the microcontroller, which, in turn, is placed on the printed circuit board with the binding to it, and then, respectively, certain modules are connected to certain legs.
I ask people who understand to throw off a good and maximally clarified example of transferring a project from Arduino to a printed circuit board. For starters, even a basic turn on / off of the LED in a second on a cycle through a logic high and low level is enough (as I understand it, this practical example is found in many textbooks).
If you are interested in the motive that I am guided by, this is an entertaining hobby, in the future I would like to make simple devices for my needs, but I am not ready to buy an additional Arduino Uno kit for each, and I consider it unreasonable. It’s better to debug everything once on Uno, sew the program into the microcontroller and transfer it to a separate board.

Answer 1

Oddly enough, very often they leave it on the Arduino in production.
With small circulations (for example, 5 pieces), this is more profitable than making a special fee, transferring something, etc., etc.

Answer 2

Here you need to understand that Arduino is a prototyping tool, i.e. you can quickly and cheaply test the circuitry and algorithm of the project. Then you have three courses of action.
1. The easiest. 1-10 device instances. You develop a power shield for your board and stupidly stick the board there.
2. More complex. Small-scale production of simple devices. You are developing a complete board on MK. In fact, the Arduino board is an Atmega 328 MK with minimal piping (the circuits are often thick and this is not necessary, but something that is not needed). The firmware is uploaded to the MK via SPI.
3. The most difficult. A completely new board is being developed, possibly with a different MK, a new program is being developed in a different programming environment in the SI language or even assembler, but taking into account the obtained algorithm. Due to the mass of features, the Arduino standard libraries have a lot of limitations and the compiler creates slow and very large code, this is not always acceptable. It also often happens that the capabilities of the Atmega 328 MK for the project being developed are unnecessary or, on the contrary, insufficient, i.e. for large-scale production, it is worth using either a simpler or more complex MK

Answer 3

The process of building an Arduino on a breadboard is described step by step in Building an Arduino on a Breadboard .
All that is required is to take the ATmega328P microcontroller, flash the Arduino bootloader into it, program the FUSE bits and after that you can use the Arduino IDE to program it.
The only thing that may be required is to create a special configuration for it, in case you want to clock your microcontroller not from a 16 MHz crystal, but, for example, from a built-in 8 MHz oscillator. In this case, you will simply need to edit the boards.txt file, adding your own configuration to it.

Answer 4

In fact, everything is exactly as you think. The only thing you have to figure out is the pinout of the bare processor, and its programming without an arduino bootloader.