cancel
Showing results for 
Search instead for 
Did you mean: 

Bluetooth SDK

wizzbert
New Contributor

For CYW920719B2Q40EVB-01, using ModusToolbox 2.2,


While trying to build the "empty_project", I get a build error that it can not link to the elf file. Build output is attached.

It is not building the elf file for the empty project. I have no idea why or even where to check the specification that it build the elf file.

Full error log attached. Per the help, this should build "out of the box" with no changes and do something simple, but it doesn't. ALL other projects build just fine, this is the ONLY one that doesn't.

>>>

Compiling V:/Software/MedPatch/MedPatchPer/template/empty_wiced_bt/build/CYW920719B2Q40EVB-01/generated/lib_installer.c  -DWICED_BT_TRACE_ENABLE -DWICED_HCI_TRANSPORT_UART=1 -DWICED_HCI_TRANSPORT_SPI=2 -DWICED_HCI_TRANSPORT=1  -DHCI_UART_MAX_BAUD=4000000 -DHCI_UART_DEFAULT_BAUD=3000000 -DSS_LOCATION=0x500000 -DVS_LOCATION=0x501000 -DDS_LOCATION=0x503000 -DDS2_LOCATION=0x582000 -DCYW20719B2=1 -DBCM20719B2=1 -DBCM20719=1 -DCYW20719=1 -DCHIP=20719 -DAPP_CHIP=20719 -DOTA_CHIP=20719 -DCHIP_REV_A_20719B2=1 -DCOMPILER_ARM -DSPAR_APP_SETUP=application_setup -D__TARGET_CPU_CORTEX_M4 -D__ARMCC_VERSION=400677 -DPLATFORM='"CYW920719B2Q40EVB_01"' -DWICED_SDK_MAJOR_VER=2 -DWICED_SDK_MINOR_VER=5 -DWICED_SDK_REV_NUMBER=0 -DWICED_SDK_BUILD_NUMBER=7341 -g3 -DSPAR_CRT_SETUP=spar_crt_setup -DCOMPONENT_SOFTFP -DCOMPONENT_bsp_design_modus -DCOMPONENT_gatt_utils_lib -DCOMPONENT_hidd_lib -I. -I../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/../../../dev-kit/btsdk-include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/WICED -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/WICED/common -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/arm -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/arm/cmsis -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/internal -I./../../../wiced_btsdk/dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/arm/cmsis -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/hal -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/internal -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/include/stack -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/baselib/20719B2/internal/20719B2 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01 -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/../../../dev-kit/btsdk-include -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus -I./../../../wiced_btsdk/dev-kit/bsp/TARGET_CYW920719B2Q40EVB-01/COMPONENT_bsp_design_modus/GeneratedSource -I./../../../wiced_btsdk/dev-kit/btsdk-include -I./GeneratedSource

    Linking output file EmptyWicedBluetooth.elf

collect2.exe: error: ld returned 1 exit status

make[1]: *** [../../../wiced_btsdk/dev-kit/baselib/20719B2/make/core/build.mk:470: V:/Software/MedPatch/MedPatchPer/template/empty_wiced_bt/build/CYW920719B2Q40EVB-01/Debug/EmptyWicedBluetooth.elf] Error 1

make: *** [../../../wiced_btsdk/dev-kit/baselib/20719B2/make/core/main.mk:350: secondstage] Error 2

"C:/ModusToolbox/tools_2.2/modus-shell/bin/make CY_MAKE_IDE=eclipse CY_MAKE_IDE_VERSION=2.2 CY_IDE_TOOLS_DIR=C:/ModusToolbox/tools_2.2 -j8 all" terminated with exit code 2. Build might be incomplete.

0 Likes
1 Solution
DheerajPK_41
Moderator
Moderator

Hi,

Ok. So we got the actual issue.

We are working with our dev team to update the offline package;s. We are looking forward to automatically post the offline packages to a public repo along with every new release of software. 

For now, if you don't want to wait till it gets updated, you can use a system with internet connected and select all the apps under 'CYW20719B2Q40EVB-01' (since current project is only with this) platform and do a one time import. Then copy the .modustoolbox cache to your offline development system and follow the instructions in the blog.  https://community.cypress.com/t5/Resource-Library/ModusToolbox-offline-libraries/ta-p/252265 

Thanks,

-Dheeraj

View solution in original post

0 Likes
8 Replies
WinstonF_61
Moderator
Moderator

Hi,

I tried building the 'Empty _project' in a clean workspace and it built successfully for me. I did a Diff of the failed build output  you sent and the one that succeeded for me. I did notice some differences. 

Seems like this project is trying to build with BTSDK ver. 2.5 instead of 2.9, is this intentional ?

 

Regards
Winston
0 Likes
wizzbert
New Contributor

The BTSDK is the offline version I could find. Apparently, I have an old version. I could see this being the issue.

Do you know where the offline version of the BTSDK 2.9 is? I am not having luck finding it (The GIT hub version looks to require internet access and my development machine is completely offline).

 

Here is the thread I pulled my BTSDK from:

ModusToolbox offline libraries - Cypress Developer Community

 

0 Likes
DheerajPK_41
Moderator
Moderator

Hi,

Could you please share the empty project which you are using? 

Also please let us know the information which we asked in https://community.cypress.com/t5/ModusToolbox-Bluetooth-SDK/Empty-project-build-fail/m-p/269136/high... 

 

Thanks,

-Dheeraj

0 Likes
wizzbert
New Contributor

Not sure what you mean, I am using the "Empty project" that is chosen from the "New application" menu, after selecting my BSP.

emtpy project.JPG

0 Likes
DheerajPK_41
Moderator
Moderator

Hi,

If you are using offline content please check this blog. https://community.cypress.com/t5/Resource-Library/ModusToolbox-offline-libraries/ta-p/252265 

 

The new software works by fetching information from manifest file hosted in github. And if you need there are ways to offload the manifest to other places/local as well. https://community.cypress.com/t5/Knowledge-Base-Articles/Offloading-the-Manifest-Files-of-ModusToolb... 

 

Your project creator tool is not fetching the latest manifest. If you have added any System variable manually as said in MTB Install guide, to pick the offline manifest, please remove those variables.

 

Thanks,

-Dheeraj

0 Likes
wizzbert
New Contributor

I checked the blog you listed and followed its recommendations. I did this for my initial setup.

Apparently, that gives me version BTSDK 2.5. Others have noted that the version I need is 2.9. Since my machine is completely offline, all paths lead back to the BTSDK of 2.5. I think this is the problem.

The system not grabbing the latest manifest, it is grabbing the only manifest that I could download and install. (The one from the offline content from the blog above, that I previously installed, that is at version 2.5).

You say delete the system variables I created, I only created the CY_TOOLS_PATH, and I believe that needs to remain. So, not sure what other variable to delete. The application tool starts and then times out trying to get online, when that happens it asks me to use the offline manifest I installed, so there is nothing further. This looks like an invalid offline content issue.

0 Likes
DheerajPK_41
Moderator
Moderator

Hi,

Ok. So we got the actual issue.

We are working with our dev team to update the offline package;s. We are looking forward to automatically post the offline packages to a public repo along with every new release of software. 

For now, if you don't want to wait till it gets updated, you can use a system with internet connected and select all the apps under 'CYW20719B2Q40EVB-01' (since current project is only with this) platform and do a one time import. Then copy the .modustoolbox cache to your offline development system and follow the instructions in the blog.  https://community.cypress.com/t5/Resource-Library/ModusToolbox-offline-libraries/ta-p/252265 

Thanks,

-Dheeraj

View solution in original post

0 Likes
wizzbert
New Contributor

Ok. Thank you for the help and replies!

0 Likes