Bootloadable *.hex and *.elf files missing

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
ROWO_285026
Level 1
Level 1
First reply posted First question asked Welcome!

I am hoping someone can help with this issue

I had rebuilt the design many times over several days as I updated the TopDesign and main.c

It was working as expected and I could build and down load to the cy8ckit-049-42xx with no issues

Changes made to the pwm are verifiable on the o-scope

Then

During a build both *.hex and *.elf files are deleted or gone

I cannot set the file paths on the dependency page as the files do not exist now

The path does not exist. per the errors

I have searched the entire drive to see if maybe they were put somewhere else but none found

Getting the following errors

error 1

pft.M0086:

Error in component: Bootloadable. The referenced Bootloader is invalid. Verify the Bootloader dependency is correct in the Bootloadable Component, then build project. Invalid bootloader hex file. Unable to read the hex file (C:\Users\Ron\Desktop\0 - ELECTRONICS\XXXXXXXX\TS_Tester\TS_Tester\My_TS_Tester.cydsn). The path does not exist.

Error2

ft.M0086:

Error in component: Bootloadable. The referenced Bootloader is invalid. Verify the Bootloader dependency is correct in the Bootloadable Component, then build project. Invalid bootloader elf file. Unable to read the elf file (C:\Users\Ron\Desktop\0 - ELECTRONICS\XXXXXXXXXX\TS_Tester\TS_Tester\My_TS_Tester.cydsn). The path does not exist.

Error3

fit.M0050:

The fitter aborted due to errors, please address all errors and rebuild.

This happened to me a couple of times in the past

The only way to get the files back is to delete the TopDesign and start over with a blank TopDesign

Comment out all the main.c changes made

Place a new Bootloadable component on the TopDesign Page

What could be suppressing the making of the *.hex and *.elf files?

Using Creator 4.2

Resources used:

digital clocks 2/4

interrupts 3/32

i/o 7/36

timer counter 3/4

udb 100%

     macro cells 10/32

     p terms 10/64

     data path 4/4

     status cells 2/4

     control cells 2/4

0 Likes
1 Solution
LinglingG_46
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 10 questions asked

From your question description, I guess you don't create a bootloader project in your workspace, the .hex and .elf file is the bootloader project generate.

From your error report, all says the bootloader is invalid.

More about the bootloader and bootloadable in PSoC4, please refer to the below linker documents:

1: https://www.cypress.com/documentation/application-notes/an73854-psoc-3-psoc-4-and-psoc-5lp-introduct...

2:https://www.cypress.com/documentation/code-examples/ce221653-psoc-4-bootloader-and-bootloadable

View solution in original post

0 Likes
1 Reply
LinglingG_46
Moderator
Moderator
Moderator
500 solutions authored 1000 replies posted 10 questions asked

From your question description, I guess you don't create a bootloader project in your workspace, the .hex and .elf file is the bootloader project generate.

From your error report, all says the bootloader is invalid.

More about the bootloader and bootloadable in PSoC4, please refer to the below linker documents:

1: https://www.cypress.com/documentation/application-notes/an73854-psoc-3-psoc-4-and-psoc-5lp-introduct...

2:https://www.cypress.com/documentation/code-examples/ce221653-psoc-4-bootloader-and-bootloadable

0 Likes