hi C,
Consider it this way, it's easier to remember what is the action sequence.
As you often say, you are having a problem in remembering, what is doing what, in the program.
This is just a suggestion to help you recall the program sequence.
Some peripheral devices are Read only, so if you made a Proc spi_rd() Call, you would remember that you need to Read the input data and store it for later processing.
If you made a Proc spi_wr Call, you would know that you have to Write to the peripheral , Command and Data and possibly not store the data Read from the peripheral
A more expanded method would be to have a Proc for each SPI connected peripheral.
eg:
Proc spi_comp()
Proc spi_bmp()
Proc sp_slave()
These Proc's would contain the Wr/Rd Address of the peripheral and the required unique named data buffers,
It sounds a little bloated, but its purpose is to help you keep track in your program
If you look back over the many years we have posted, it is constantly coming back to what you have forgotten
E
Consider it this way, it's easier to remember what is the action sequence.
As you often say, you are having a problem in remembering, what is doing what, in the program.
This is just a suggestion to help you recall the program sequence.
Some peripheral devices are Read only, so if you made a Proc spi_rd() Call, you would remember that you need to Read the input data and store it for later processing.
If you made a Proc spi_wr Call, you would know that you have to Write to the peripheral , Command and Data and possibly not store the data Read from the peripheral
A more expanded method would be to have a Proc for each SPI connected peripheral.
eg:
Proc spi_comp()
Proc spi_bmp()
Proc sp_slave()
These Proc's would contain the Wr/Rd Address of the peripheral and the required unique named data buffers,
It sounds a little bloated, but its purpose is to help you keep track in your program
If you look back over the many years we have posted, it is constantly coming back to what you have forgotten
E