- Joined Aug 2, 2022
It is a good idea to make a code in an Arduino first before to implement in another microcontoller?
IMO, only if working within the same architectural uC family. But if you are going to implement on another "Arduino" fully supported board, I think it is OK to start prototyping ideas until you procure the needed Arduino board.
Yes, but if he uses libraries he will be in for a huge mess in porting. I am not sure why he needs to move to a different MCU and development platform. If he can write what he wants in the Arduino IDE then he can use the code directly by using the same MCU, be can much more easily clear away the board definition than port the libraries.It depends. Forth has been used to quickly mock up models of software systems, sometimes to be re-written in a more widely recognized language. Forth has the advantage of easy to use to express ideas and actions. If Arduino is a very easy platform for you to use, go ahead and use it to mock up and experiment with your ideas. After that you can move it, for example, to a $2 microcontroller if you were careful to keep resource limitations in mind.
It is much like I rough out magazine articles in html then transfer to word for submission.
Sounds... tedious.Changing microcontrollers is hugely time consuming. I have just moved software from a 64-pin NXP LPC1517 to a Renesas RA4M1, both of which are 32-bit ARMs with the same instruction set, and both have the same set of peripherals but the peripheral control registers all are different.
It has taken months.
I very rarely make flow charts, except when I work with others as a team. What I always do though, is write in plain and simple language every step (and why) of what the code is supposed to do.Actually, it's a good idea to flow-chart your code before implementing it in any MCU or PCU.
The first time I did NOT in more than 15 years, it was in my (almost finished) current project. Thanks to that I made the stupid mistake of calling an obstructive online delay in the middle of the main loop. Had to debug to know why.Actually, it's a good idea to flow-chart your code before implementing it in any MCU or PCU.
That is, in and of itself a form of a 'flow-chart'. It is a logic methodology that works for you. Flow-charts should be done by newer coders- it gives them a road-map that they can 'run' on paper and test scenarios and check their logic. More seasoned/veteran coders use flow-charting less because they have usually learned 'tried and true' methods to code defensively- like always niling pointers after use, and so forth.I very rarely make flow charts, except when I work with others as a team. What I always do though, is write in plain and simple language every step (and why) of what the code is supposed to do.
|Thread starter||Similar threads||Forum||Replies||Date|
|Need an idea on a connector type||Datasheets, Manuals & Parts Identification||0|
|J||1st time designing with logic chips. Check my idea?||Digital Design||14|
|J||How to make flow chart and write code for actual idea ?||Programming & Languages||23|
|M||8051 code in C language which can be tested using KEIL, NO IDEA AT ALL!||Homework Help||20|
|F||Vhdl code help plz...cant get any idea..||Microcontrollers||0|
by Jake Hertz
by Aaron Carman
by Jake Hertz