Help in understanding and documenting some 8052 code
$30-250 USD
진행 중
게시됨 2년 이상 전
$30-250 USD
제출할때 지불됩니다
I need some help in embedded 8051 development, specifically a person who can analyze existing code and add comments to help make understandable by the others. The environment is Codeblocks IDE with 8051/2 micro and SDCC compiler.
Let me explain more. I am a salesperson in the IoT in a developing country. My customers have applications for some very nice IoT radios using the 8052. However, the existing code to develop with these is complex and not so well documented. I am missing applications opportunities by not being able to explain things better to my customers.
The code is spread out across many include files, some libraries, several nests of programs. There is a lot of inline assembler code. I have a newbie, still recovering my c skills, learning Codeblocks, advanced debugging, etc. Its going too slow. I need an experience embedded developer to help me understand things better when I get stuck. All of the source code is available and there is a lot of existing. I just need someone to help me sort things out and comment some programs better. We don't have to comment everything.. Just enough to make thing clearer in several critical areas.
The developer I am looking for will know:
Codeblocks IDE
SDCC compiler and details like sdcc_external_startup, stack initialization, building libraries, inline assembler.
8051/2 architecture,programming, interrupts
functional english - the ability to look at a function and comment it so another developer can understand it. I am looking for communications skills that can help other developers how to develop with the products.
Debugging. Deciphering multiple levels of a call stack, maybe the lower levels doing inline code, etc. Watches.
I wish to start with a simple task of better documenting some timing interrupt routines. Any person trying to use these parts need to make timer interrupt calls and distinguish between Cold and warms startup context. If the successful candidate can improve the documentation on this code effectively. We can continue to other parts and build a relationship.
I know exactly how you feel, deciphering C code can be seriouslt confusing because it's usually spread over os many files. I've done thins quote a lot and I'm sure I could help you.