Hi to all..
Well after thinking a lot I see that are some thing that can't be done in the AccessB like:
- Exact timming control, so applications that use capture or compare modules will can't work properly, but all the configuration word for capture and compare and access to SFR and bits can be done.
- The hardware part of the project is only to serve as pin control, data adcquisition, serial bus communications, etc. the data will be always be processed by the software, so save data in GPR isn't necessary then access to GPR isn't implemented.
- The hardware always work with a Host connected and the Host give the power source to the board, so there isn't necessary to save data in the EEPROM, the project isn't planned to work as a stand alone module.
All the firmware in the PIC uses about 50% of the program memory and that 50% is almost all the functions that I will program, there are two functions that I want to program in the firmware and software class but it will take more time:
- JTAG
- User Defined Functions (UDF): well almost 50% of the program memory will be unused so I want to give the software and firmware the ability to program itself like a bootloader and the firmware can execute that code like a extra function, so the user can make his own firmware function in MPLABX XC8 (that is free to use both) and program in the unused program memory space using an application, and with the class the user can call that function, so in that case the user can have more timming control and it can use capture an compare modules, use the EEPROM or process data inside the PIC.
Discussions
Become a Hackaday.io Member
Create an account to leave a comment. Already have an account? Log In.