Calling Kinetis bootloader from application results in unexpected behavior in GPIOs

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Calling Kinetis bootloader from application results in unexpected behavior in GPIOs

875件の閲覧回数
s_ff
Contributor I

From the KL17 RM I can see below pins are used for pinmuxing by the Kinetis bootloader. 

sina_farzinfar1_0-1679505857818.png

But calling the bootloader from the application, I'm experiencing some pins that are not in the above list (ex PTB17) lose their modes and become floating while some other pins keep their modes (output on/off). Since the bootloader resides in the ROM section, is there anything I should do in the application before calling the bootloader to keep the state of the GPIO pins? Is the bootloader (at offset 0x1C00_0000) de/re initializes all the pins or just the enabled peripherals? Could you give more details?

ラベル(1)
タグ(1)
0 件の賞賛
返信
1 返信

821件の閲覧回数
CarlosGarabito
NXP TechSupport
NXP TechSupport

Hi @s_ff  Are you using a custom board? Have you tried the program without any connection on the MCU? Or have you tried to do the same with the FRDM-KL27?

0 件の賞賛
返信