- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm using CYBT-423028-EVAL-01.
I installed the SDK following the instructions in the package (refer to KBA223637). The WICED studio still have problem resolving symbols. I have both CYBLE920719Q40EVB-01 and CYBT-423028-EVAL-01. It seems the system can not decide which one to use when I compile. The .h files looks very
here's how wiced_platform.h looks like from the first directory:
here's how wiced_platform.h looks like from the second directory.
Except the line number is different, everything else looks the same. From previous posts, it may seem like this isn't an issue for other people. I can't say it's the same for me.
Any idea on how to tell the compiler to use which .h file? otherwise, i'll just have to use GPIO_EN_INT_BOTH_EDGE.
interrupt configs seem to work, but PLATFORM_GPIO_0 through PLATFORM_GPIO_15 are problematic.
Thanks!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try the following operation:
Right click on the platform file -> properties -> C/C++ Build -> Uncheck the box "Exclude resource from build" -> Apply -> OK.
Then right click on the 20719-B1_Bluetooth and refresh the file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you using the demo code hello_sensor? Do you chang the name of the make target as the KBA says: demo.hello_sensor-CYBT_423028_EVAL download ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yes, that's exactly what i have.
Any idea why it's still not recognizing the symbols?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Which version of the SDK are you using? I just test it with 6.2.1.2. It works fine.
The platform files must be used with WICED 6.2 or later.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I start to think this is the problem. Do you see anything different than what I'm seeing under platform? Mine is deprecated. I don't think I manually deprecated it, but how do you get it back to normal?
I'm using 6.2. Here's my configuration details.
*** Date: Monday, October 22, 2018 at 9:20:34 AM Pacific Daylight Time
*** Platform Details:
*** System properties:
applicationXMI=org.eclipse.ui.workbench/LegacyIDE.e4xmi
awt.toolkit=sun.awt.windows.WToolkit
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=4.4.2.M20150204-1700
eclipse.commands=-os
win32
-ws
win32
-arch
x86
-showsplash
c:\program files\wiced-studio-6.2\ide\\plugins\org.eclipse.platform_4.4.2.v20150204-1700\splash.bmp
-launcher
c:\program files\wiced-studio-6.2\ide\eclipse.exe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
one more screen shot of what I'm looking at:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please try the following operation:
Right click on the platform file -> properties -> C/C++ Build -> Uncheck the box "Exclude resource from build" -> Apply -> OK.
Then right click on the 20719-B1_Bluetooth and refresh the file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't think I can uncheck both platforms at the same time, but I can at least uncheck the one I'm using at the moment and that seems to solve the problem.
Thanks a lot!