Shooting : place your code to flash area for flash dialog
operation. And place your code to RAM area for RAM booting dialog
operation.
Shooting : place your code to flash area for flash dialog operation. And place your code to RAM area for RAM booting dialog operation.
Trouble: Failed to enter bootloader mode
Shooting :
Mainly due to wrong hardware connection between easyDSP and your MCU board.
Step 1 : please check if your connection is correct. Hope you find misconnection in this step. Or, move to step 2.
Step 2 : please check the waveforms of easyDSP pins during booting. Also refer to the below sequence of easyDSP pin status.
In case /RESET of easyDSP is NOT directly connected to reset pin of MCU, please check reset pin status of DSP pin directly.
Step 2-1 : please check if BOOT pin is high when /RESET pin is changed from low to high.
In case power monitoring IC (TPSxxxx) is used to generate NRST signal and /RESET is an input to the IC,
it could happen that NRST becomes high after BOOT is low, which will make booting failure.
Step 2-2 : please check RX and TX. After BOOT pin is low, 0x7F (even parity) is sent from PC to MCU via RX.
Bauding bps could be either 115200bps or 57600bps or other value depending of MCU type.
Then MCU send 0x79 (even parity) to PC at the detected bps. With this handshake, bps of each side (easyDSP and MCU) are aligned.
In case you can't observe 0x79 at all, please modify the option byte accordingly.
Trouble: Failed to enter bootloader mode 2
After entering the bootloader, the STM32 MCU scans multiple communication channels for incoming input and activates the bootloader based on that channel with incoming input. If easyDSP is connected to USART1 and another communication device is connected to USART2, a signal on the USART2 RX line right after easyDSP resets the MCU to enter the bootloader may cause the bootloader to operate based on USART2, not USART1, which leads to a bootloader failure.
Solution: Starting from easyDSP version 12.7, MCU is informed that MCU reset for bootloader will take place approximately 200 msec later. This allows the MCU to take necessary actions. To implement these actions, users must manually code the following section in easyStm32LL.c.
In this case, a request could be sent to the communication device connected to USART2 to stop communication. This ensures that after the reset, valid signals are generated only on USART1 (where easyDSP is connected), allowing the system to successfully enter the bootloader.
