> Do these mode have commonly used names ? If so, it could be useful and > easier for users to provide procedures like spi_set_mode_indredible() or > spi_set_mode_amazing(), ... This would help to hide complexity (if it is a > good idea to hide complexity).
the mode names are 0,0 0,1 1,0 and 1,1 as in this chart: -- SPI Mode Name - CKP CKE -- 0,0 - 0 1 -- 0,1 - 0 0 -- 1,0 - 1 1 -- 1,1 - 1 0 hence the original _spi_init_mode00 The problem is that 16F877 uses these registers: SSPCON_CKP = 0 -- idle state for clock is high level SSPSTAT_CKE = 0 -- clock edge select, data transmitted on falling and 18F452 uses the following: SSP1CON_CKP = 0 -- idle state for clock is high level SSP1STAT_CKE = 0 -- clock edge select, data transmitted on falling As william stated, we do not want a large, complex lib file that is hard to maintain. i suggested using many different example files instead. How do you think this should be done seb? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jallib?hl=en -~----------~----~----~----~------~----~------~--~---
