Home
last modified time | relevance | path

Searched +full:rv32m1 +full:- +full:port (Results 1 – 12 of 12) sorted by relevance

/Zephyr-latest/dts/bindings/gpio/
Dopenisa,rv32m1-gpio.yaml3 compatible: "openisa,rv32m1-gpio"
5 include: [gpio-controller.yaml, base.yaml]
14 "#gpio-cells":
17 openisa,rv32m1-port:
22 port associated with this GPIO controller.
24 gpio-cells:
25 - pin
26 - flags
/Zephyr-latest/dts/riscv/openisa/
Drv32m1.dtsi3 * SPDX-License-Identifier: Apache-2.0
6 #include <zephyr/dt-bindings/interrupt-controller/openisa-intmux.h>
7 #include <zephyr/dt-bindings/gpio/gpio.h>
8 #include <zephyr/dt-bindings/i2c/i2c.h>
9 #include <zephyr/dt-bindings/pwm/pwm.h>
12 #address-cells = <1>;
13 #size-cells = <1>;
17 zephyr,flash-controller = &ftfe;
21 #address-cells = <1>;
22 #size-cells = <0>;
[all …]
/Zephyr-latest/boards/openisa/rv32m1_vega/doc/
Dindex.rst8 The VEGAboard contains the RV32M1 SoC, featuring two RISC-V CPUs,
9 on-die XIP flash, and a full complement of peripherals, including a
10 2.4 GHz multi-protocol radio. It also has built-in sensors and
11 Arduino-style expansion connectors.
13 The two RISC-V CPUs are named RI5CY and ZERO-RISCY, and are
15 `RI5CY`_ and `ZERO-RISCY`_. RI5CY is the "main" core; it has more
16 flash and RAM as well as a more powerful CPU design. ZERO-RISCY is a
17 "secondary" core. The main ZERO-RISCY use-case is as a wireless
30 RV32M1 multi-core SoC:
32 - 1 MiB flash and 192 KiB SRAM (RI5CY core)
[all …]
/Zephyr-latest/doc/releases/
Drelease-notes-1.14.rst17 * CVE-2020-10066
18 * CVE-2020-10069
19 * CVE-2020-13601
20 * CVE-2020-13602
32 * :github:`issuenumber` - issue title
34 * :github:`18334` - DNS resolution is broken for some addresses in master/2.0-pre
35 * :github:`19917` - Bluetooth: Controller: Missing LL_ENC_RSP after HCI LTK Negative Reply
36 * :github:`21107` - LL_ASSERT and 'Imprecise data bus error' in LL Controller
37 * :github:`21257` - tests/net/net_pkt failed on mimxrt1050_evk board.
38 * :github:`21299` - bluetooth: Controller does not release buffer on central side after peripheral …
[all …]
Drelease-notes-2.0.rst12 * The kernel now supports both 32- and 64-bit architectures.
17 * We added support for :ref:`Point-to-Point Protocol (PPP) <ppp>`. PPP is a
20 * We added support for UpdateHub, an end-to-end solution for large scale
21 over-the-air device updates.
22 * We added support for ARM Cortex-R Architecture (Experimental).
32 * Fixes CVE-2019-9506: The Bluetooth BR/EDR specification up to and
35 negotiation. This allows practical brute-force attacks (aka "KNOB")
42 * New kernel API for per-thread disabling of Floating Point Services for
43 ARC, ARM Cortex-M, and x86 architectures.
45 * Additional support for compatibility with 64-bit architectures.
[all …]
Drelease-notes-2.2.rst18 * Fix CVE-2020-10028
19 * Fix CVE-2020-10060
20 * Fix CVE-2020-10063
21 * Fix CVE-2020-10066
32 * :github:`23494` - Bluetooth: LL/PAC/SLA/BV-01-C fails if Slave-initiated Feature Exchange is disa…
33 * :github:`23485` - BT: host: Service Change indication sent regardless of whether it is needed or …
34 * :github:`23482` - 2M PHY + DLE and timing calculations on an encrypted link are wrong
35 * :github:`23070` - Bluetooth: controller: Fix ticker implementation to avoid catch up
36 * :github:`22967` - Bluetooth: controller: ASSERTION FAIL on invalid packet sequence
37 * :github:`24183` - [v2.2] Bluetooth: controller: split: Regression slave latency during connection…
[all …]
Drelease-notes-2.3.rst18 with future support for features like 64-bit and absolute timeouts in mind
21 * Zephyr now integrates with the TF-M (Trusted Firmware M) PSA-compliant
24 * The CMSIS-DSP library is now included and integrated
33 * CVE-2020-10022: UpdateHub Module Copies a Variable-Sized Hash String
34 into a fixed-size array.
35 * CVE-2020-10059: UpdateHub Module Explicitly Disables TLS
37 * CVE-2020-10061: Improper handling of the full-buffer case in the
39 * CVE-2020-10062: Packet length decoding error in MQTT
40 * CVE-2020-10063: Remote Denial of Service in CoAP Option Parsing Due
42 * CVE-2020-10068: In the Zephyr project Bluetooth subsystem, certain
[all …]
Drelease-notes-3.1.rst61 * Split CAN classic and CAN-FD APIs:
90 was moved from Kconfig to :ref:`devicetree <dt-guide>`.
91 See the :dtcompatible:`st,stm32f1-pinctrl` devicetree binding for more information.
182 * MIPI-DSI
184 * Added a :ref:`MIPI-DSI api <mipi_dsi_api>`. This is an experimental API,
196 * Added support for enabling/disabling CAN-FD mode at runtime using :c:macro:`CAN_MODE_FD`.
220 * Added support for Provisioners over PB-GATT
231 * Implemented ISO-AL TX unframed fragmentation
232 * Added support for back-to-back receiving of PDUs on nRF5x platforms
249 newly created informational-only callback struct :c:struct:`bt_conn_auth_info_cb`.
[all …]
Drelease-notes-2.4.rst33 * CVE-2020-10060: UpdateHub Might Dereference An Uninitialized Pointer
34 * CVE-2020-10064: Improper Input Frame Validation in ieee802154 Processing
35 * CVE-2020-10066: Incorrect Error Handling in Bluetooth HCI core
36 * CVE-2020-10072: all threads can access all socket file descriptors
37 * CVE-2020-13598: FS: Buffer Overflow when enabling Long File Names in FAT_FS and calling fs_stat
38 * CVE-2020-13599: Security problem with settings and littlefs
39 * CVE-2020-13601: Under embargo until 2020/11/18
40 * CVE-2020-13602: Remote Denial of Service in LwM2M do_write_op_tlv
50 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
62 * The :c:func:`wdt_feed` function will now return ``-EAGAIN`` if
[all …]
Drelease-notes-2.6.rst13 * Added support for 64-bit ARCv3
14 * Split ARM32 and ARM64, ARM64 is now a top-level architecture
15 * Added initial support for Arm v8.1-m and Cortex-M55
22 https://github.com/zephyrproject-rtos/example-application
34 * CVE-2021-3581: Under embargo until 2021-09-04
41 <https://github.com/zephyrproject-rtos/zephyr/issues?q=is%3Aissue+is%3Aopen+label%3Abug>`_.
46 * Driver APIs now return ``-ENOSYS`` if optional functions are not implemented.
47 If the feature is not supported by the hardware ``-ENOTSUP`` will be returned.
48 Formerly ``-ENOTSUP`` was returned for both failure modes, meaning this change
194 * Added support for null pointer dereferencing detection in Cortex-M.
[all …]
/Zephyr-latest/doc/hardware/porting/
Dboard_porting.rst21 - Support for multi-core, multi-arch AMP (Asymmetrical Multi Processing) SoCs
22 - Support for multi-SoC boards
23 - Support for reusing the SoC and board Kconfig trees outside of the Zephyr
25 - Support for advanced use cases with :ref:`sysbuild`
26 - Removal of all existing arbitrary and inconsistent uses of Kconfig and folder
38 Some non-critical features, enhancements and improvements of the new hardware
47 with two options if they have an out-of-tree board (or SoC):
49 #. Convert the out-of-tree board to the current hardware model (recommended)
57 can then use the `example-application conversion Pull Request`_ as an example on
58 how to port a simple board. Additionally, a `conversion script`_ is available
[all …]
/Zephyr-latest/
DMAINTAINERS.yml45 # files-regex:
56 # files-exclude:
59 # files-regex-exclude:
60 # Like 'files-regex', but any matching files will be excluded from the
63 # description: >-
64 # Plain-English description. Describe what the system is about, from an
68 # All areas must have a 'files' and/or 'files-regex' key. The other keys are
72 # this would be sub-areas which add extra fields (for ex. more `collaborators`
73 # who work only in that sub-area) to other areas.
98 # Collaborators: <list of sub-maintainers>
[all …]