1. 04 Sep, 2020 3 commits
  2. 03 Sep, 2020 1 commit
  3. 02 Sep, 2020 3 commits
  4. 01 Sep, 2020 3 commits
    • Simon Glass's avatar
      native_posix: Use the I2C emulator for the EEPROM test too · b3f0c79e
      Simon Glass authored
      
      At present this test uses an EEPROM emulator. Reuse the same test to
      also use the real Atmel AT2x driver and an AT24 emulator, via the I2C
      emulation controller.
      
      EEPROM reads and writes for eeprom1 go through the AT2x driver, which
      converts them to I2C transactions, which are passed through to the
      AT24 emulator for processing. This approach makes more use of 'real'
      code, in this case the Atmel AT2x driver.
      Signed-off-by: default avatarPeter Bigot <peter.bigot@nordicsemi.no>
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      b3f0c79e
    • Simon Glass's avatar
      emul: i2c: Add support for I2C emulators · 49f21679
      Simon Glass authored
      
      Add an emulation controller which routes I2C traffic to attached
      emulators depending on the I2C address selected. This allows drivers
      for I2C peripherals to be tested on systems that don't have that
      peripheral attached, with the emulator handling the I2C traffic.
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      Signed-off-by: default avatarPeter Bigot <peter.bigot@nordicsemi.no>
      49f21679
    • Simon Glass's avatar
      emul: Create an emulation implementation · 302d671e
      Simon Glass authored
      
      Create a header file and implementation for emulators. Set up a linker
      list so that emulators can be found and initialised at start-up.
      
      Emulators are used to emulate hardware devices, to support testing of
      various subsystems. For example, it is possible to write an emulator
      for an I2C compass such that it appears on the I2C bus and can be used
      just like a real hardware device.
      
      Emulators often implement special features for testing. For example a
      compass may support returning bogus data if the I2C bus speed is too
      high, or may return invalid measurements if calibration has not yet
      been completed. This allows for testing that high-level code can
      handle these situations correctly. Test coverage can therefore
      approach 100% if all failure conditions are emulated.
      Signed-off-by: default avatarPeter Bigot <peter.bigot@nordicsemi.no>
      Signed-off-by: default avatarSimon Glass <sjg@chromium.org>
      302d671e
  5. 28 Aug, 2020 1 commit
    • Maxime Bittan's avatar
      boards: arm: add FaZe board support · a9573e44
      Maxime Bittan authored
      
      The FaZe board can be found in the Seagate FireCuda Gaming SSD devices.
      A NVMe SSD and two chips are embedded: an ASMedia ASM2364 USB-to-PCIe
      bridge controller and a NXP LPC11U67 MCU. The former is handling the USB
      type-C to SSD I/Os while the latter is dedicated to the LED effects. The
      two chips are connected together through I2C and GPIOs.
      
      This Zephyr port is running on the LPC11U67 MCU.
      
      Here is a list of the devices connected to the LPC11U67 on a FaZe board:
      
      - ASMedia ASM2364 USB-to-PCIe bridge (I2C master on port O)
      - 6 RGB LEDs connected connected to a TI LP5030 LED controller
        (I2C device on port 1)
      - 1 white LED (SSD activity blinking)
      Signed-off-by: default avatarMaxime Bittan <maxime.bittan@seagate.com>
      Signed-off-by: default avatarSimon Guinot <simon.guinot@seagate.com>
      a9573e44
  6. 26 Aug, 2020 1 commit
  7. 25 Aug, 2020 2 commits
    • Daniel Leung's avatar
      tests: add a test for coredump · 86b2cbc5
      Daniel Leung authored
      
      This adds a simple test for coredump.
      Signed-off-by: default avatarDaniel Leung <daniel.leung@intel.com>
      86b2cbc5
    • Daniel Leung's avatar
      debug/coredump: add a primitive coredump mechanism · 49206a86
      Daniel Leung authored
      
      This adds a very primitive coredump mechanism under subsys/debug
      where during fatal error, register and memory content can be
      dumped to coredump backend. One such backend utilizing log
      module for output is included. Once the coredump log is converted
      to a binary file, it can be used with the ELF output file as
      inputs to an overly simplified implementation of a GDB server.
      This GDB server can be attached via the target remote command of
      GDB and will be serving register and memory content. This allows
      using GDB to examine stack and memory where the fatal error
      occurred.
      Signed-off-by: default avatarDaniel Leung <daniel.leung@intel.com>
      49206a86
  8. 24 Aug, 2020 2 commits
  9. 14 Aug, 2020 2 commits
  10. 13 Aug, 2020 5 commits
  11. 06 Aug, 2020 2 commits
  12. 04 Aug, 2020 1 commit
  13. 03 Aug, 2020 2 commits
  14. 31 Jul, 2020 1 commit
  15. 29 Jul, 2020 1 commit
  16. 24 Jul, 2020 3 commits
  17. 20 Jul, 2020 1 commit
  18. 17 Jul, 2020 1 commit
  19. 13 Jul, 2020 1 commit
    • Gerson Fernando Budke's avatar
      boards: shields: Introduce atmel_rf2xx module shield · 9e45fefc
      Gerson Fernando Budke authored
      
      The Atmel RF2xx module shield is a generic solution to enable any Atmel
      AT86RF2xx IEEE 802.15.4 transceiver. This module enables IEEE 802.15.4
      RF2xx Zephyr driver.
      
      The Atmel RF2xx module shield enables any board with an Atmel Xplained,
      Xplained-Pro, Arduino or MikroBus expansion header to connect to
      networks operation with IEEE 802.15.4, OpenThread or any other stack
      based on this media type.
      
      The Atmel RF2xx module is configured to allow interoperate with other
      medias like Ethernet. User need configure network stack properlly.
      
      Fixes #26259.
      Signed-off-by: default avatarGerson Fernando Budke <nandojve@gmail.com>
      9e45fefc
  20. 01 Jul, 2020 4 commits