I apologize if you think I was posting in a sarcastic manner, I assure you that was not my intentions; but I was NOT posting blindly. I have read every post you have posted since joining the forum and out of the current 105, at least 80 are direct requests for personal assistance with some at-the-moment issue as you work through the port of the Atmega AVR port of your project to STM32duino. From ILI9341, to SD, to LCD backlight, to blue pill issues, to bootloader problems, to ENRF24, and now to Software serial.konczakp wrote:@mrburnette Since a few posts You are saying how wrong I am and how badly is my project designed in a sarcastic way which is impolite IMO. While You have nothing to say in the subject of this topic!
I tried to help you the other day when I said you were going down the rabbit hole. In all of the 105 posts, only snippets of your code have been shared which is OK except for the continuing number of problems you are facing. In my world, the design process you are following is called "shotgunning" and what one gets is a tangled mess of spaghetti code that is going to be a freaking nightmare to maintain in the future... assuming you ever get the port working successfully at all. You have already stated that the AVR version of the project was a terrible mess to support; do you really think this STM version will be better if you are stitching piece to piece to piece to ... ?
Now while I was not trying to be sarcastic, I am saying that your approach to design is less than optimal: and I suspect time will prove me correct in saying that you are creating a support nightmare. Selecting a $2 uC appears to simply be a poor decision based upon your continuing issues.
PS: Yes, I am an ass ... I am a system architect and being an ass is part of my job description when the telling is the truth.