Problem with linker script when changing from CYPD3125 to CYPD3123 with SDK 3.4

Announcements

Live Webinar: USB-C adoption. Simple & Cost-efficient solutions | April 18th @9am or 5pm CEST. Register now !

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

cross mob
OlEr_1999891
Level 5
Level 5
50 replies posted 25 replies posted 25 sign-ins

Hi!

When I copy and compile the standard CYPD3125-40LQXI_notebook.cydsn project from the 3.4 Host SDK both backup_fw and main fw compiles without problem. However, when I change to CYPD3123 (via Device Selector) and change the bootloader to "CYPD3123-40LQXI_usb_boot_3_0_2_900_0_0_0_cu.hex", I get: 

ERROR: cannot open linker script file .\cm0g_1.ld: No such file or directory
collect2.exe: error: ld returned 1 exit status
The command 'arm-none-eabi-gcc.exe' failed with exit code '1'.

when building the project. Tried without success:

- Renaming cm0gcc.ld to cm0g_1.ld, but there was no  cm0gcc_2.ld in the project folder 
- Copy cm0g_1.ld / cm0g_2.ld from the backup_fw projet

Do I need a new USB bootloader file for the 3.4 SDK? Or does the linker-files need to change to fit in the USB booatloader?

Cheers

Olof

0 Likes
1 Solution
ShifangZ_26
Moderator
Moderator
Moderator
10 likes given 250 sign-ins 1000 replies posted

Hello Olof,

1. You shall update the usb boot in Application FW2 only same as Host SDK and make sure back up project have been complied successful. 

2.. If you are using MDK complier with host SDK3.4, your question is correct, the CYPD3123 usb boot need a new .elf and .hex file for usb boot. 

Best Regards,

Lisa

View solution in original post

0 Likes
5 Replies