CC2564: Changing default flash location

Antenna_Head

Part Number: CC2564

On behalf of customer:

...regarding CC2564 Bluetooth Classic with STM32F407, all mostly works fine. I need to load firmware to location 0x08008000 instead of 0x08000000 in flash.

I already created a bootloader project which load in 0x08000000 location and perform jump to 0x08008000 location.

I made one very simple project which load on 0x08008000 location ( just turn on LED). It's work fine.

But, when I use Bluetooth sample code ( modifying in keil project option the address to 0x08008000 and doing the same in linker tab and scatted file. I also change Vector address to 0x8000 instead of 0x00), it got hardware fault.

Looking to the behavior, I suspect some other thing also need to change for this method.

What else needs to be changed to move this code to 0x08008000?

Thanks!

-Steve

over 2 years ago

0 Ryan T over 2 years ago

TI__Intellectual 2961 points

Hi Steve,

Is the customer trying to load the firmware at a different location on the transceiver? If so, the memory that they are writing to is read-only, which would make sense to have a hardware fault. Moving the firmware on the CC2564 is not supported by the device.

Please let me know if I can be of more assistance.

Best,

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

No, they are trying to relocate the code on the ST processor. Suspect it might be a problem with a compile binary library or something, looking for hints here as to where to look for the problem.

0 Ryan T over 2 years ago in reply to Antenna_Head

TI__Intellectual 2961 points

Hi Steve,

Can you please ask the customer to use the default .bts file for loading the firmware on the device? The default should work for them in this case.

Best,

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

Are you suggesting this as a debug idea? They probably want/need to move the code for a specific reason otherwise they would already be loading it to the standard address.

0 Ryan T over 2 years ago in reply to Antenna_Head

TI__Intellectual 2961 points

Hi Steve,

Yes I am suggesting that they check the default .bts to ensure that the only issue that they are seeing is with moving the firmware address.

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

From customer:

Stock firmware project works perfectly. No issue at all, because stock firmware uses flash sector 0.

0 Ryan T over 2 years ago in reply to Antenna_Head

TI__Intellectual 2961 points

Hi Steve,

Please disregard what I had mentioned previously--after pulling in another member of the team and walking through it, we realized I had misunderstood the issue.

For changing the address of the firmware address on the host, please consult the ST forums. They would have better information about their hardware capabilities.

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

sorry, I'm having trouble finding the forum you're referring to. Can you move it or otherwise show me which one it is?

0 Ryan T over 2 years ago in reply to Antenna_Head

TI__Intellectual 2961 points

Please consult this forum with ST Micro: https://community.st.com/s/

They will have more in-depth information about moving firmware on the STM32.

BR,

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

This doesn't appear to be an ST problem, per the customer:

I don’t think it’s st side. Because if I create project without CC2564 stack( meaning not using radio) I manage to run from other location of flash without any issue.

I think in stack something need to be done or it does not allow to run from other flash sector location.

I suspect there is some portability issue with the stack, especially if it's a compiled library and maybe it's not linking properly.

0 Ryan T over 2 years ago in reply to Antenna_Head

TI__Intellectual 2961 points

Hi Steve,

Let me consult with the rest of my team to see if there are any known issues relating to this. I will follow up shortly.

Best,

-Ryan

0 Ryan T over 2 years ago in reply to Ryan T

TI__Intellectual 2961 points

Hi Steve,

Providing a quick update--after talking more with other members of the applications team, we may be able to resolve this issue using relative addressing--I will reply to the thread tomorrow with more information and actionable steps to try and resolve the issue.

Best,

-Ryan

0 Ryan T over 2 years ago in reply to Ryan T

TI__Intellectual 2961 points

Hi Steve,

I'm sure you have already checked for this, but for my sanity, have you checked that the memory allocated for Bluetopia is the same as before with the default?

Additionally, are there any other debug logs that you can provide outside the hardware fault? How is the bootloader project transitioning to 0x0800800 made?

Best,

-Ryan

0 Antenna_Head over 2 years ago in reply to Ryan T

TI__Genius 11885 points

Thanks, will get back to you soon. -Steve

Bluetooth®︎

Bluetooth forum

CC2564: Changing default flash location