• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 783 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Boundary tool for OS X?

pixbroker
Genius 5820 points


CCS for OS X now supports CC26XX which is great. I was able to compile and link the SBP project. However, the post build step fails due to lack of Boundary tool. Is the Boundary tool going to be ported to OS X or what is the solution going to be on that platform?

Thanks.

  • 0
    TI__Guru** 105180 points
    Hello,

    There are no plans to port Boundary.exe to OSX. You can manually set the ICALL_STACK/RAM0 boundaries and disable the Boundary tool by following the guidance in the BLE SW Developer's Guide (SWRU393).

    Best wishes
  • 0 in reply to JXS
    Genius 5820 points
    Thanks JXS. What's the recommended way to determine the correct values for manually setting the stack/ram boundary in this case?
  • 0 in reply to pixbroker
    Prodigy 190 points
    I've had success running Boundary.exe under mono, which I installed using MacPorts.

    Building on MacOS X is very similar to building on Linux (without many of the case mismatch problems.) That's now been documented at processors.wiki.ti.com/.../Building_BLE_Projects_on_Linux though I've always used mono to run Boundary.exe rather than wine as documented there.
  • 0 in reply to Norman Mackenzie
    Genius 5820 points

    Interesting, thanks for the tip. Out of curiosity, do you also use mono to install the blue stack? i tried:

    mono ble_cc26xx_setupwin32_2_01_00_44423.exe 

    but get:

    Cannot open assembly 'ble_cc26xx_setupwin32_2_01_00_44423.exe': File does not contain a valid CIL image.

  • 0 in reply to pixbroker
    Prodigy 190 points

    The installer and the libSearch.exe pre-build step are win32 apps, so I used wine for those.

    On OS X, the installation of the stack and the setup of the pre and post-build steps was essentially the same as I'd used before for running on Linux.  That's described at https://e2e.ti.com/support/wireless_connectivity/f/538/t/412962  I went through the same process on OS X when CCS 6.1.1 became available for the Mac.

    Boundary.exe is a .NET app.  I think recent versions of wine will automatically download and install a copy of mono to run .NET apps, but my Linux system runs an older version of Ubuntu with a version of wine that didn't do this.  I had to install and call mono explicitly to run Boundary.exe.  Using wine instead of mono to run Boundary.exe should work on OS X, but I've not tried it.  I know that using mono directly can work.