Hi?
I am using Arduino uno, I want to design a new board. must I use the chip Atmel 16U2.
Is it just a chip convert USB to Serial. I do not have space for it on the board.
Give me some advises. Thanks
You don't need any of those if you program it with the ISP interface.
Nor do you need it if you develop the sketch on your Uno board and when complete remove the 328p chip and place it in your standard-alone board. Using a 28 pin socket in your project would be needed to make this practical.
Or add a header to plug in an FTDI Basic or equivalent for programming/debugging, unplug when done.
You can see one at the bottom left here:
HI?
Thanks very much.
It means the chip is only a USB to Serial.
I can program the 328 by the ICSP with a cable.
The cable can be bought or make a uno acted as a programmer?
Still using the arduino IDE to program 328?
Thanks
Arnold_Sweden:
HI?
Thanks very much.
It means the chip is only a USB to Serial.
I can program the 328 by the ICSP with a cable.
The cable can be bought or make a uno acted as a programmer?
Still using the arduino IDE to program 328?
Thanks
Overview:
Gammon Forum : Electronics : Microprocessors : How to make an Arduino-compatible minimal board
One thing you can't do via ICSP is debugging with Serial.print statements.
The USB/Serial is key for that.
CrossRoads:
One thing you can't do via ICSP is debugging with Serial.print statements.
The USB/Serial is key for that.
Technically, yes, Serial.print or MySerial.print needs an output pin, but a $2 buy-it-now/freeship usb-serial Silicon Chip CP210x will do nicely. It is not that it needs to be dedicated to the project.
Heck, for $15 you can build my dedicated serial terminal and test gen:
http://www.hackster.io/rayburne/the-qbf-signal-generator
Serial is useful for debugging but I recommend debugging on the "real" arduino and then sanity checking on the deployed hardware config... In this case, Serial() may even be disabled entirely to recover a few resources.
Ray
Having a Serial header to plug an FTDI Basic or equivalent (CP2102) makes that easy.
CrossRoads:
Having a Serial header to plug an FTDI Basic or equivalent (CP2102) makes that easy.
I cannot disagree with that... A 5-pin male or female header is small-cost item. But, thinking back to 30+ months of projects, I have never used serial debugging once a project left the bench. So, even a 5¢ part does not need to be sacrificed for no return value!
I come from a very methodical engineering environment where great expenditures are spent providing coders with "promotional" environments:
- Development
- Unit test
- System test
- Pre-production
- Production
The system test, pre-prod, and prod environments are identical in hardware and softwares stack but the physical RAM and #CPU may be different between Pre-prod and System test. Prod/pre-Prod are identical with pre-Prod serving as Prod during product upgrades... Hence, if necessary, the machine roles could be reversed by simply changing TCP-IP addresses.
Point is, there is a place for debugging in the software maturity model, but as one moves forward, the need should become nil. Even in s 3-level model, the final phase should not have debugging active, IMO..
Ray
If you want to take that design and repurpose it, the header makes it easy to re-kickoff the design.
CrossRoads:
If you want to take that design and repurpose it, the header makes it easy to re-kickoff the design.
touché
As it turns out, I do use a 3-step model and stage1 and stage2 do have have dedicated serial connections. However, the Prod Stage does not... So, no bootloader and no bloat for debug code.
Ray