Hi
I have an application that uses an STM32F105RBT6 ant its USB peripheral as host mode connected to a HID controller, and driving a few GPIOs connected to 74HC04 inputs.
The application was created using firmware package 1.7.0 and STM32CubeMx with a Makefile and linux toolchain.
The application has been enhanced on a F205 board with STM32CubeIDE, where it is working well, and the enhancements are being backported to the F105 with 1.8.4 firmware package. I write "backported" however it is mostly the same code, but the pinouts are different.
There, I have a strange behavior :
PB3, pin 55 on the package, which is a simple Push-pull GPIO output, does not work on the updated app with 1.8.x firmware with the F105 board. What is strange is that on the scope it is stuck flat to a 0.3v level, which is slightly higher than the other outputs at their low level : as if the pin was not set like the others.
The outputs are set just with the generated HAL configuration and HAL WritePin inside the USBH process loop.
HAL_GPIO_WritePin(B_UP_GPIO_Port, B_UP_Pin, !gamePorts[1].u); <- u,d,l,r are uint8_t in the gamePorts struct
HAL_GPIO_WritePin(B_DOWN_GPIO_Port, B_DOWN_Pin, !gamePorts[1].d);
HAL_GPIO_WritePin(B_LEFT_GPIO_Port, B_LEFT_Pin, !gamePorts[1].l);
HAL_GPIO_WritePin(B_RIGHT_GPIO_Port, B_RIGHT_Pin, !gamePorts[1].r); <- this is the PB3 pin not working
- All the other GPIO outputs are working as intended.
- The problem is the same on all the F105 boards I tried, and all of these boards are working when they are downgraded with the old 1.7.0 application, so it seems this is not a hardware problem (bad chip, solder joint, pcb).
- Changing the order of WritePin calls changes nothing.
- When swpapping the values that are written to these outputs, the other GPIO are working well with the swapped values, but still not this PB3 "B_RIGHT_Pin".
- When debugging the app and, using STM32CubProgrammer, dumping memory of the "gamePorts" structure that stores the values that are applied to the GPIO output, all the values are correct.
- The pin configuration in gpio.c seems OK, identical to the others.
- This is not a define/naming problem, HAL_GPIO_WritePin(GPIOB, GPIO_PIN_3, (gamePorts[1].r?GPIO_PIN_RESET:GPIO_PIN_SET)) does the same.
- The only peripherals that are used are TIM7 and USB_OTG_FS/USB_HOST, and GPIOs at low speed with a few interrupts. All are set through the STMcubeIDE graphical interface.
I have tried firmware package 1.8.4 and 1.8.0 and both have the same result.
I have read the STM32F105 device errata but nothing seems relevant.
Everything else in the application works fine (especially usb setup and communication), it is frustrating to be blocked by something apparently so trivial.
By chance would someone have a clue or ideas of other things to try ?
