cancel
Showing results for 
Search instead for 
Did you mean: 

PSoC 4 MCU

Anonymous
Not applicable

I created a project with a bootloader and a bootloadable component. I've designed the bootloader to wait 2 second then run the application. The application will launch into a reset if a certain register gets written to. Giving a custom bootloader host a chance to write a new application.

My problem is on startup the bootloader never exits and waits for a command forever. Debugging it the application id being valid is failing and therefore its running the bootloader forever. Am I doing something wrong?

0 Likes
Reply
13 Replies
JoMe_264151
Expert II

I would suggest to uncheck the option "Accept matching Address in Rx"

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

Just tried that. No luck.

0 Likes
Reply
JoMe_264151
Expert II

What is your underlying hardware (Kit? Which??) and what progammer do you use?

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

Chip: CY8C4014LQI-422
Programmer/Debugger: MiniProg 3

The chip is connected to a 3x9 touchpad and acts as a slave device. Beyond that the touchpad board is connected by I2C to an Android CPU. It wouldn't enumerate in that environment. I've disconnected it from the CPUto see if there was a problem between the two, but I still see the issue with the board disconnected. There are 5 debug pins that on the board that our connected to the MiniProg 3.

The unit works when I disable the bootloadable component.

0 Likes
Reply
Anonymous
Not applicable

Bob, I wonder if this is same type problem I was having when using bootloader and bootloadable,,,ie if we modify lower flash (ie flash not outside the area in which checksum is calculated) it causes the bootloader to sense a corrupt load and always run.  I was using Em_eeprom so that may have been a different issue but it sounds like the same problem I was having.

0 Likes
Reply
JoMe_264151
Expert II

Use the flash area below the MetaData area and in bootloader component specify to exclude the used amount of flash from checksum generation.

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

How do I do that?

0 Likes
Reply
JoMe_264151
Expert II

Use the flash area below the MetaData area. Have a look at the memory maps in the bootloader datasheet.

   

In the "System Reference guide" (Creator -> Help) you find descriptions of flash APIs and defined constants.

   

The bootloader config has an entry for excluding that area from calculating the checksum.

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

Do you mean start the application program right below the metadata area? And then exclude the bootloader area from the checksum?

0 Likes
Reply
JoMe_264151
Expert II

No.

   

Use one or two flash rows right below the metadata area for your emeeprom.

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

I don't have an emeeprom in my design. 

0 Likes
Reply
JoMe_264151
Expert II

I was reflecting to R.Thomas post. You did not disagree with his assumption yet.

   

 

   

Bob

0 Likes
Reply
Anonymous
Not applicable

It sounded like that could be part of the problem. I don't have the eeprom, but was wondering if anything in my project would of caused a similar problem.

0 Likes
Reply