Corrected my correction of my misunderstanding of how SGPIO_CTRL_ENABLE works. Turns out I *can* immediately disable a slice using ENABLE. If I want to synchronously disable a slice, I do it via DISABLE. And if I want to screw up my code, I (unwittingly) set all slices to synchronously disable, then configure SGPIO and watch my slices run once and stop. :-( All better now.
This commit is contained in:
@ -133,7 +133,7 @@ void test_sgpio_interface() {
|
|||||||
|
|
||||||
void configure_sgpio_test_tx() {
|
void configure_sgpio_test_tx() {
|
||||||
// Disable all counters during configuration
|
// Disable all counters during configuration
|
||||||
SGPIO_CTRL_DISABLE = 0xFFFF;
|
SGPIO_CTRL_ENABLE = 0;
|
||||||
|
|
||||||
configure_sgpio_pin_functions();
|
configure_sgpio_pin_functions();
|
||||||
|
|
||||||
@ -199,7 +199,7 @@ void configure_sgpio_test_tx() {
|
|||||||
|
|
||||||
void configure_sgpio_test_rx() {
|
void configure_sgpio_test_rx() {
|
||||||
// Disable all counters during configuration
|
// Disable all counters during configuration
|
||||||
SGPIO_CTRL_DISABLE = 0xFFFF;
|
SGPIO_CTRL_ENABLE = 0;
|
||||||
|
|
||||||
configure_sgpio_pin_functions();
|
configure_sgpio_pin_functions();
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user