This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Dear TI experts,
We have a custom board that has AM2634 Microcontroller,
1) We are able to flash in JTAG mode or Dev boot mode and code runs fine without any issues.
2) When we flash using UART uniflash tool to external memory we are getting POR pin toggling which means its resetting continuously/
How can we overcome the POR reset or stop the POR reset ?
Hi Prashanth Arun,
1) We are able to flash in JTAG mode or Dev boot mode and code runs fine without any issues.
Do you mean JTAG Uniflash ? If not, Can you try via JTAG Uniflash ?
Here is an FAQ demonstrating the same - https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1227707/faq-mcu-plus-sdk-am263x-faq-how-to-flash-the-application-via-jtag-or-sbl-jtag-uniflash
2) When we flash using UART uniflash tool to external memory we are getting POR pin toggling which means its resetting continuously/
In case of UART Boot mode if the ROM Bootloader is unable to fetch an image within 180secs i.e. 3 mins, it will reset the device. However this won't happen in Dev Boot mode as ROM execution completes and stops in UART Boot Mode.
Best Regards,
Aakash
Hi Aakash Kedia,
1) Tried JTAG uniflash method by using scripting console --> POR pin is resetting.
Question: We are using S25FL128LAGMFB013 intead of S25FL128SAGNF1000.
The only difference that we see in the chip changes is JEDEC device id:
S25FL128LAGMFB013 --> uses 0x6018 as JEDEC device id
S25FL128SAGNF1000 --> uses 0x2018 as JEDEC device id which is currently on the CC development board.
Hence we used example codes of Uart_uniflash and SBL_qspi code and changed the sysconfig of FLASH JEDEC device id to 6018 and rebuilded flash writer and SBL_QSPI images.
Does ROM bootloader support if we use different FLASH chip(S25FL128LAGMFB013) in our case ?
As ROM bootloader is not configurable is the ROM boot still looking for JEDEC flash id of 0x2018 ?
Hi Aakash Kedia, Issue solved now, it was because of External WDG resets. when we refreshed the WDG the issue got solved.
Thanks & Regards,
Prashanth Arun