Skip to content
Permalink
Branch: master
Commits on Jul 22, 2019
  1. samples: usb: console: Remove overlay file

    carlescufi committed Jul 22, 2019
    After the removal of the virtualcom DT node in 5071eee, using the chosen
    node is no longer functional. Instead the Kconfig
    CONFIG_UART_CONSOLE_ON_DEV_NAME is used to locate the correct UART.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. boards: nrf52840_pca10059: Enable ADC in DT

    carlescufi committed Jul 22, 2019
    Enable the ADC in the basic DT configuration.
    
    Fixes #17671
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Jul 18, 2019
  1. west: Load CMakeCache.txt as a UTF-8 encoded file

    carlescufi committed Jul 18, 2019
    CMake has been using UTF-8 as an encoding for CMakeCache.txt since 3.2.
    
    Fixes #17635
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. cmake: Encode and decode in UTF-8 in build system

    carlescufi committed Jul 18, 2019
    In order to make sure that the build works in folders that require a UTF
    encoding, make sure that both CMake and the various Python scripts that
    interact with each other on files use the same encoding, in this case
    UTF-8.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Jun 28, 2019
  1. drivers: rtc: Adapt to new counter API

    carlescufi authored and galak committed Jun 28, 2019
    The counter API changed recently, and more specifically the
    counter_set_top_value() now takes a configuration structure instead of
    direct parameters. Adapt the rtc.h header so that it uses the new
    signature correctly.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Jun 26, 2019
  1. west: runners: Guess build folder

    carlescufi authored and nashif committed Jun 17, 2019
    When using a build folder format with build.dir-fmt that includes any
    parameters that need resolving, the west runners cannot find the folder
    since the required information (board, source dir or app) is not
    available.
    Add a very simple heuristic to support the case where a build folder
    starts with a hardcoded prefix (for example 'build/') and a single build
    is present under that prefix.
    The heuristic is gated behind a new configuration option:
    build.guess-dir
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. Bluetooth: hci_uart: Assert if device is NULL

    carlescufi committed Jun 20, 2019
    Assert if the UART device is NULL to help with debugging whenever
    there's an issue locating the correct UART instance.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  3. Bluetooth: hci_uart: Use DT for the hci_uart UART

    carlescufi committed Jun 20, 2019
    Use Device Tree,and in particular a new 'bt-c2h-uart' to select which
    UART is being used to communicate with an external BLE Host when acting
    as a Controller.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Jun 17, 2019
  1. doc: extensions: Default to 'all' in 'tool'

    carlescufi authored and andrewboie committed Jun 14, 2019
    In order to expose west to the majority of users, default to 'all'
    instead of 'cmake' in the 'tool' option. This means that, unless
    otherwise specified, build instructions will be generated for both west
    and cmake by default.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. doc: Cleanup references to cmake

    carlescufi authored and andrewboie committed Jun 13, 2019
    Clean up some stray references to cmake in doc, boards and
    samples that don't make explicit use of the zephyr app extension,
    as well as other minor doc fixes.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  3. doc: extensions: Refactor cmake build instructions generation

    carlescufi authored and andrewboie committed Jun 13, 2019
    In order to simplify the current implementation and to prepare for a
    change where we default to west as the standard build tool, partially
    refactor the generation of cmake-based build instructions:
    
    - Introduce `cd-into` as boolean flag that controls whether build
    instructions are generated from the current working directory or from
    inside the actual app folder. In the case of cmake, this includes
    changing into the build folder to run ninja or make.
    
    - Default to building from the current working directory, in the case of
    cmake using the `-B` flag to create the build folder.
    
    - Remove the usage of ZEPHYR_BASE with the `zephyr-app` option.
    The option itslef is kept fsince it has semantic value, and a comment is
    added when used.
    
    - Consolidate the _generate_make and _generate_ninja functions into a
    common code block inside _generate_cmake.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Jun 10, 2019
  1. west: build: Configurable build folder format

    carlescufi committed Jun 5, 2019
    Add the possibility of configuring the build folder format in west's
    configuration system.
    The build.dir-fmt configuration option controls how west will create
    build folders when not specified, the following parameters are currently
    accepted:
    
    - board: The board name
    - source_dir: The relative path from CWD to the source directory
    - app: The name of the source directory
    
    If CWD is below source_dir in the directory hierarchy then source_dir is
    set to an empty string.
    
    This means that if one sets:
    
    [build]
    dir-fmt = build/{board}/{source_dir}
    
    Then when building samples/hello_world from zephyr's root for the
    reel_board the build folder will be:
    
    ./build/reel_board/samples/hello_world
    
    but when building it from inside the samples/hello_world folder it will
    instead be:
    
    ./build/reel_board
    
    Fixes zephyrproject-rtos/west#124
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
    Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
  2. west: Use find_build_dir in run_common

    carlescufi committed Jun 3, 2019
    In preparation for upcoming changes to the way the default build folder
    is defined, switch to using the common find_build_dir() function in the
    runners.
    This actually changes the behavior for the west build command slightly,
    since the current working directory (cwd) will now be checked after the
    default build folder ('build'). This brings it in line with what is
    used for the runners.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 24, 2019
  1. doc: CMake: Locate Python executable before processing modules

    carlescufi committed May 23, 2019
    The module processing logic in Zephyr requires Python, since it uses a
    Python script to locate and process the modules. It is therefore
    required to find the Python executable using CMake before actually
    including the CMake script that processes the modules. In order to
    prevent this from happening again, move the inclusion of version.cmake
    as well in case that script chooses to use Python in the future.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. cmake: Fix path handling for ZEPHYR_BASE

    carlescufi committed May 23, 2019
    With the addition of a local CMake variable ZEPHYR_BASE that mirrors the
    value of the environment variable the documentation build broke on
    Windows. This is because CMake was incorrectly interpreting backslashes
    present in the Windows path as escaping characters. In order to avoid
    this, use CMake's built-in file(TO_CMAKE_PATH) functionality, which
    converts the path to a canonical version using forward slashes only.
    At the same time rework boilerplate.cmake to use the same mechanism
    instead of manually replacing backslashes and removing trailing ones.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 15, 2019
  1. doc: coding style: Expand the list of keywords with braces

    carlescufi authored and galak committed May 15, 2019
    Zephyr requires braces on every code block that a keyword introduces, so
    list the complete set in the documentation.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. samples: basic: Add a minimal sample

    carlescufi committed May 9, 2019
    Add a minimal sample that showcases minimal ROM sizes. It can be built
    in several configurations, all very restrictive when it comes to
    features enabled in order to verify the fact that we can fit in small
    devices and to be able to accurately measure the sizes of the kernel's
    basic features.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  3. soc: nrf: Conditionally enable clock control and timer

    carlescufi committed May 9, 2019
    The CONFIG_CLOCK_CONTROL and CONFIG_NRF_RTC_TIMER were
    unconditionally selected when enabling any nRF SoC. But since
    timers can be disabled in the kernel, depend instead on
    CONFIG_SYS_CLOCK_EXISTS, which is only defined when kernel
    timer support is included.
    
    Note that ideally we would enable CONFIG_NRF_RTC_TIMER only, and
    that would select CONFIG_CLOCK_CONTROL (on which the RTC timer
    depends) but there is a circular Kconfig dependency that prevents
    us from doing so.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  4. kernel: Fix usage of CONFIG_SYS_CLOCK_EXISTS

    carlescufi committed May 9, 2019
    When compiling the kernel with CONFIG_SYS_CLOCK_TICKS_PER_SEC=0,
    the CONFIG_SYS_CLOCK_EXISTS internal variable is unset.
    This completely disables timer handling in the kernel, but a couple of
    spots missed the required conditional compilation.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 14, 2019
  1. tests: counter: Enable nRF52810 testing

    carlescufi committed May 13, 2019
    Enable the counter capability in the board and add a .conf file for the
    nRF52810 running on the PCA10040 board.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. boards: holyiot_yj16019: Remove counter from supported

    carlescufi committed May 13, 2019
    The supported field is used by sanitycheck to select which tests will be
    run on a particular board. The issue with the counter drivers, and in
    particular on nRF ICs, is that the timer peripherals are disabled by
    default and need to be enabled on a per-board basis inside a .conf file.
    Since this board doesn't have a .conf file in
    tests/drivers/counter/counter_basic_api/boards/ the test cannot be run
    on this board.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 10, 2019
  1. doc: west: Document west installation in-depth

    carlescufi committed May 8, 2019
    Create a new dedicated section for west installation that details
    some of the finer aspects of the process and steps involved.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. west: Add completion command

    carlescufi committed May 8, 2019
    Add a completion command that dumps the contents of a shell
    completion file present in the zephyr repository.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  3. west: Add bash completion file

    carlescufi committed May 8, 2019
    This file was previously located in the west repository, under scripts/.
    Since it now includes knowledge about specific behavior ef zephyr
    extension commands, we move it here after overhauling it completely.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 6, 2019
  1. Bluetooth: controller: hal: Fix PPI macro naming

    carlescufi committed May 6, 2019
    Due to a protracted merge of:
    5e38ed9
    the naming for the HAL_SW_SWITCH_RADIO_ENABLE_S2_PPI changed
    semnatics, now requiring use of
    HAL_SW_SWITCH_RADIO_ENABLE_S2_PPI_BASE.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 5, 2019
  1. west: boards: Use the new zcmake module name

    carlescufi committed May 4, 2019
    Switch to the recently renamed zcmake module when importing the
    run_cmake function.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 4, 2019
  1. west: build: Construct CalledProcessError with positional args

    carlescufi committed May 4, 2019
    Since west's main.py relies on the args tuple with the returncode
    and the cmd, create the CalledProcessError using the correct
    positional args.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on May 3, 2019
  1. west: Add a boards command

    carlescufi committed Apr 23, 2019
    Add a new "boards" command that is able to list all the boards in the
    upstream tree. There is currently no support for out-of-tree boards.
    
    The command executes cmake to use the built-in CMake script,
    boards.cmake, to list the boards, and then stores the information
    retrieved and allows the user to present it in a user-definable format.
    
    Fixes zephyrproject-rtos/west#53
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. west: Implement CMake helpers in scripts/west_commands

    carlescufi committed Apr 26, 2019
    Move the existing CMake and build functionality from the west repository
    to zephyr. The rationale behind this move is that it's very tightly
    coupled with the Zephyr build system and is only used by the extension
    commands implemented in the zephyr tree.
    If additional extension commands in third-party repos want to use the
    functionality they can add $ZEPHYR_BASE/scripts/west_commands to the
    Python system path.
    
    The implmentations in the west repo will be deprecated.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Apr 25, 2019
  1. cmake: Split out board listing from usage

    carlescufi committed Apr 22, 2019
    In order to make board listing reusable by external tools, split it out
    from the usage helper script into a new boards.cmake that can also be
    called directly with cmake -P.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Apr 23, 2019
  1. scripts: west: Run pristine.cmake directly instead of the target

    carlescufi committed Apr 18, 2019
    When making a build folder pristine until now we were running the
    'pristine' build target. The issue with that is that ninja/make or
    whatever build tool is being used might decide to re-run CMake itself if
    some of the dependencies have changes. This might trigger an error that
    is unfriendly and unnecessary, since the user is explicitly asking for
    the build folder to be wiped before starting a fresh build.
    To avoid this issue restor to running directly the CMake script that the
    'pristine' build target itself uses, so as to make sure that the build
    folder is wiped unconditionally regardless of changes made to the tree.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Apr 19, 2019
  1. drivers: Bluetooth: Generalize IC-specific setup hook

    carlescufi committed Apr 18, 2019
    In order to generalize the currently specialized nRF51 IC setup hook,
    make the following changes:
    
    - Generalize the hook to bt_ic_setup()
    - Use a weak NOP version by default
    - Move the currently existing one to the board folder
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Apr 18, 2019
  1. doc: extract_content: Allow for absolute paths in deps

    carlescufi authored and nashif committed Apr 4, 2019
    The dependencies in the scripts are figures, images, includes or literal
    includes. Typically those dependencies are placed relative to the .rst
    file that is being copied, but in some instances you might want them to
    refer to an absolute path which, in fact, is relative to Sphinx's
    top-level source directory. In this case, and as long as the top-level
    source directory is provided, do not emit a warning.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Commits on Apr 17, 2019
  1. west: build: Add new pristine cmd-line and config option

    carlescufi authored and nashif committed Apr 14, 2019
    Add a new command-line and build config option, `pristine`, that the
    user can pass to `west build` or set in its configuration file(s) in
    order to automatically trigger a pristine build on every build or
    whenever west considers it required.
    
    The option can take the following values:
    
    - never: Never run the target
    - always: Always run the pristine target before building
    - auto: Run the pristine target when required
    
    With `auto`, the pristine target will be run when running
    west with an existing build folder containing a build system and:
    
    - Selecting a different board from the one currently in the build system
    - Selecting a different application from the one currently in the build
      system
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
  2. west: build: Use officially documented CMake options

    carlescufi authored and nashif committed Apr 14, 2019
    The -B option has always existed but was first officially documented in
    CMake 3.13.0. In that same release the -S option was introduced,
    replacing the old undocumented -H. Switch to using the officially
    documented options.
    
    Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
Older
You can’t perform that action at this time.