WICED Build error: 'OTA2_IMAGE_FLASH_BASE' undeclared

[GrCa_1363456]

Please provide some ideas why a build of one project fails while others succeed?

Building test.console (a project included with WICED) works fine on two different PCs. Building test.at_cmd (a project provided by Murata) fails on one specific computer. It works on the other computer. The computer it works on has been running WICED for many years. The computer it fails on is at a different company and recently loaded WICED. WICED has been removed and reinstalled several times with no major improvements.

The error is:

libraries/filesystems/ota2/./wiced_ota2_image.c: In function 'wiced_ota2_image_copy_uncompressed_component':
libraries/filesystems/ota2/./wiced_ota2_image.c:577:19: error: 'OTA2_IMAGE_FLASH_BASE' undeclared (first use in this function); did you mean 'PLATFORM_FLASH_BASE'?

The full console output is attached for the PC that fails and for the PC that passes.

Greg

[Aditi_B]

Hi,

Is it possible to provide the project/code example? Is it a snip application of WICED or a custom project?

Thanks

Aditi

[GrCa_1363456 · Accepted solution]

Aditi,

The issue appears to have been with the path name in Windows. There were spaces in either the location where WICED was installed or the workspace. The spaces appear to have been the result of Microsoft OneDrive implementation. There seems to be a method to hide the full pathname of the Documents directory in Windows. Use the Command Prompt to see the full name. 

Open Command Prompt. Type DIR. Look for a directory starting with the name "OneDrive....". Change Directories into the OneDrive... directory by typing CD followed by the directory name. Note there's a "Documents" directory under the "OneDrive..." directory. That's the directory that shows up in Windows file explorer. However, WICED sees the full path name. If the "OneDrive..." name has spaces or other characters that WICED doesn't like, there's likely to be inconsistent issues.

Greg

[Aditi_B]

Thanks for the update. I suppose the issue is resolved now, right?