- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- Wireless Connectivity
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- MCUXpresso Training Hub
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
-
- Home
- :
- General Purpose Microcontrollers
- :
- Kinetis Microcontrollers
- :
- Re: Kea Bootloader AN5400
Kea Bootloader AN5400
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Kea Bootloader AN5400
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Guys, I am trying to use the Bootloader PC software and firmware from nxp AN5400 and i have some problems. The software PC works quite well but i have problems when I upload by means of Application a new firmware (I used one of an example of SDK frdm.128 and freedom board FRDM-128). The problems is that the new firmware doesn't work even if the procedure is correct. I noticed that if I launch from debug (s32) the application firmware, it works very well. I'am going mad because i can't explain this behavior. The firwmare is present from the address 0x1000 f MCU but it doesnt' work.
Someone have experienced with this problem?
Martino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
mjbcswitzerland Hello Mark, thank u for the hints, but i didn't solved the problem. I try to give more details about this problem. I noticed in debug that the CNT register of RTC is stuck to 0 and it never go on. This is the reason that the application doesn't work. it's more strange because how i told you the application "standalone" works very well. So what I am doing wrong?
Thank you!
Martino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
If the loaded application runs but not the RTC then there is presumably a problem with the RTC code being used. Without knowing the clock that you are using and the code it is not possible to say what the problem is. However, I do remember analysing PE generated RTC code that is buggy and sometimes fails as detailed here: Running the K64 from its RTC oscillator - does it work? Although I doubt it to be an explanation in this case it shows that you will basically need to debug the code and correct whatever is stopping it working as expected (not all code is fool-proof when not used in the single way that it was tested in).
Regards
Mark
P.S. For the FRDM-KEAZ128 you can also try a loader and application from http://www.utasker.com/kinetis/FRDM-KEAZ128Q80.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Mark, Finally I solved the problem I mentioned here. The problem was a uncorrect clock configuration (ICS). In particular in bootloader KEA the clock ICS is engaged internally (FEI) but in the application code ICS is engaged esternally (FEE) . I tried to change the ICS configuration on the boot code and magically every pheripheral (also the RTC) worked very well. By the way thank you for your suggest. I tried to download utasker but after I got the login I didn't download the source from the repository. Is it possible to have another login or refresh the old one? Thank you
Martino
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Martino
I am glad to hear that you solved the problem.
Regards
Mark
P.S. Since you were also registered as uTasker free commercial user I have re-activated your private account for an extension (5 days).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Have you linked the application correctly so that it can start at its shifted start address?
See appendix B of the following document for a list of things to check when working with boot loaders: http://www.utasker.com/docs/uTasker/uTaskerSerialLoader.PDF
It also explains various alternative boot loaders available for your chip.
Regards
Mark
