mlower

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • in reply to: Nordic nRF5x SDK11.0 Release #7864
    mlower
    Participant

    The newest version on nordic website is 11.0 “production ready”: http://developer.nordicsemi.com/nRF5_SDK/nRF5_SDK_v11.x.x/ This is stable version certified by Bluetooth SIG and the first stable version for nRF52 series. Also this is the first version that unifies development between nRF51 and 52 series. Your BSP generator doesn’t work with this and modifications that I’ve tried to make allow to generate BSP pack but code doesn’t compile.

    in reply to: Cannot debug after upgrading to JLink software 5.10q #7765
    mlower
    Participant

    Version 5.10s works. Firmware update crashes Visual Studio but this happens only once so it’s not a big problem.

    in reply to: Launch failed when flashing without debugging #7520
    mlower
    Participant

    I still get the same error. I’ve tried on new and existing project.

    in reply to: Toolchain failure after the NRF5x Ver 2.0 update #7412
    mlower
    Participant

    That’s because there was an SDK update. BSP 2.0 is bundled with SDK 10.0. Previous was using SDK 9.0. Among other things app_timer stuff was changed. You have to correct all timer declarations in you code. My project wasn’t compiling at first after the change too. Apart from timer init you have replace all app_timer_id variables with APP_TIMER_CREATE macro and define timer scheduler handler.

    • This reply was modified 8 years, 4 months ago by mlower.
    in reply to: Toolchain failure after the NRF5x Ver 2.0 update #7410
    mlower
    Participant

    Same thing happens for me. Every time I change VisualGDB project properties I get “the commandline is too long” popup window. Clicking ‘ignore’ allows me to skip the error and so far my nRF51 projects compile fine.

Viewing 5 posts - 1 through 5 (of 5 total)