| /Zephyr-latest/soc/altr/zephyr_nios2f/cpu/ |
| D | ghrd_10m50da.qsf | 9 # to the terms and conditions of the Altera Program License
15 # authorized distributors. Please refer to the applicable
81 set_location_assignment PIN_N14 -to clk_ddr3_100_p
82 set_location_assignment PIN_M8 -to clk_25_max10
83 set_location_assignment PIN_N5 -to clk_10_adc
84 set_location_assignment PIN_P11 -to clk_lvds_125_p
85 set_location_assignment PIN_T20 -to user_led[0]
86 set_location_assignment PIN_U22 -to user_led[1]
87 set_location_assignment PIN_U21 -to user_led[2]
88 set_location_assignment PIN_AA21 -to user_led[3]
[all …]
|
| /Zephyr-latest/samples/drivers/soc_flash_nrf/ |
| D | README.rst | 5 Use the flash API to interact with the SoC flash.
11 The sample uses :ref:`Flash map API <flash_map_api>` to obtain a device that has one
13 to directly access and modify the contents of a device within the area defined for said
17 are performed on a device, and how to first check whether device is
47 Attempted to write 1122 at 0x82000
48 Attempted to read 0x82000
51 Attempted to write aabb at 0x82004
52 Attempted to read 0x82004
55 Attempted to write abcd at 0x82008
56 Attempted to read 0x82008
[all …]
|
| /Zephyr-latest/drivers/sensor/honeywell/mpr/ |
| D | Kconfig | 20 bool "0 to 1"
22 bool "0 to 1.6"
24 bool "0 to 2.5"
26 bool "0 to 15"
28 bool "0 to 25"
30 bool "0 to 30"
32 bool "0 to 60"
34 bool "0 to 100"
36 bool "0 to 160"
38 bool "0 to 250"
[all …]
|
| /Zephyr-latest/tests/boards/mec172xevb_assy6906/i2c_api/ |
| D | README.txt | 4 This application test is used to test the I2C driver on Microchip
12 to I2C00 port, however, I2C00 port is shared with UART2 RS232 to TTL
13 converter used to catch serial log, so it's not possible to use UART2
15 We need to change to use I2C01 port by making some jumpers setting as below:
17 * JP49 1-2 Connected Connect PCA9555 VCC to +3.3V_STBY
19 * JP12 13-14 Connected Connect I2C01_SDA from CPU to header J20
20 * JP12 4-5 Connected Connect I2C01_SCL from CPU to header J20
25 * JP58.1 J20.1 Connected Connect NXP PCA95xx to I2C01
26 * JP58.3 J20.3 Connected Connect NXP PCA95xx to I2C01
|
| /Zephyr-latest/tests/boards/mec15xxevb_assy6853/i2c_api/ |
| D | README.txt | 4 This application test is used to test the I2C driver on Microchip
12 to I2C00 port, however, I2C00 port is shared with UART2 RS232 to TTL
13 converter used to catch serial log, so it's not possible to use UART2
15 We need to change to use I2C01 port by making some jumpers setting as below:
17 * JP99 1-2 Connected Connect I2C01_SDA from CPU to header J5
18 * JP99 13-14 Connected Connect I2C01_SCL from CPU to header J5
22 * JP44.1 J5.1 Connected Connect NXP PCA95xx to I2C01
23 * JP44.3 J5.3 Connected Connect NXP PCA95xx to I2C01
|
| /Zephyr-latest/samples/drivers/led/xec/ |
| D | README.rst | 10 This sample allows to test the Microchip led-xec driver which uses the
41 - Connect GPIO 0156 to board LED4 by placing a wire from JP71-11 to J47-3.
45 - Connect GPIO 0156 to board LED5 by placing a wire from JP71-12 to J48-3.
49 - Connect GPIO 0153 to board LED7 by placing a wire from JP71-5 to JP146-5.
51 JP146-5 is connected to MEC172x VCI_OUT1 without a jumper. Force VCI_OUT1
53 to the VBAT rail via a 100K pull-up. Requires VBAT power rail is connected
54 to VTR or some other power source.
57 - Connect GPIO 0035 to board LED7 by placing a wire from JP67-19 to JP146-1.
60 JP146-1 is connected to MEC172x VCI_OUT2 without a jumper. Force VCI_OUT2
62 to the VBAT rail via a 100K pull-up. Requires VBAT power rail is connected
[all …]
|
| /Zephyr-latest/soc/xlnx/zynq7000/xc7zxxx/ |
| D | Kconfig.soc | 20 2 ARM Cortex-A9 cores up to 866 MHz, Artix-7 programmable logic,
21 28k logic cells, 2.1Mb block RAM, 800 DSP slices, up to 100 I/O pins.
27 2 ARM Cortex-A9 cores up to 866 MHz, Artix-7 programmable logic,
28 74k logic cells, 3.3Mb block RAM, 160 DSP slices, up to 150 I/O pins,
29 up to 4 transceivers.
35 2 ARM Cortex-A9 cores up to 866 MHz, Artix-7 programmable logic,
36 85k logic cells, 4.9Mb block RAM, 220 DSP slices, up to 200 I/O pins.
42 2 ARM Cortex-A9 cores up to 1 GHz, Kintex-7 programmable logic,
43 125k logic cells, 9.3Mb block RAM, 400 DSP slices, up to 250 I/O pins,
44 up to 4 transceivers.
[all …]
|
| /Zephyr-latest/doc/develop/getting_started/ |
| D | installation_mac.rst | 12 Terminal application (or any other terminal emulator) are subject to the same
13 system security policies that are applied to applications launched from the
15 macOS will not let you execute those from the Terminal by default. In order to
18 * Run ``xattr -r -d com.apple.quarantine /path/to/folder`` where
19 ``path/to/folder`` is the path to the enclosing folder where the executables
20 you want to run are located.
23 and then scroll down to "Developer Tools". Then unlock the lock to be able to
24 make changes and check the checkbox corresponding to your terminal emulator of
25 choice. This will apply to any executable being launched from such terminal
28 Note that this section does **not** apply to executables installed with
[all …]
|
| /Zephyr-latest/subsys/sd/ |
| D | Kconfig | 11 Enable MMC protocol support. Required for eMMC cards to function.
16 Enable SDMMC protocol support. Required for SD memory cards to
22 Enable SDIO protocol support. Required for SD I/O cards to function.
41 Maximum time to wait, in milliseconds, for the SD card to initialize.
44 int "Number of times to retry initialization commands"
47 Number of times to retry initialization commands in case of failure
50 int "Number of times to retry SD OCR read"
53 Number of times to retry SD OCR read command. OCR reads typically
73 # If MMC is being used, need 512 bytes to read EXT_CSD
75 # If SDIO is being used, need 512 bytes to read FUNC0 CIS
[all …]
|
| /Zephyr-latest/cmake/toolchain/llvm/ |
| D | clang_libgcc.cfg | 3 # Tell clang to give us the actual path to libgcc.a
5 # decide to return path to libclang_rt.* if its default
6 # is to use that library. Since we do -lgcc by default,
7 # better tell clang to give us the correct path to libgcc.a.
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/timer_synchronization/ |
| D | README.rst | 4 Use timers and message queues from CMSIS RTOS v1 API to synchronize threads.
11 The main thread creates a preemptive thread which writes message to message queue
17 This project outputs to the console. It can be built and executed
32 Wrote to message queue: 5
35 Wrote to message queue: 6
38 Wrote to message queue: 7
41 Wrote to message queue: 8
44 Wrote to message queue: 9
47 Wrote to message queue: 10
50 Wrote to message queue: 11
[all …]
|
| /Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/ |
| D | README.rst | 4 Use timers and message queues from CMSIS RTOS v2 API to synchronize threads.
11 The main thread creates a preemptive thread which writes message to message queue
17 This project outputs to the console. It can be built and executed
32 Wrote to message queue: 5
35 Wrote to message queue: 6
38 Wrote to message queue: 7
41 Wrote to message queue: 8
44 Wrote to message queue: 9
47 Wrote to message queue: 10
50 Wrote to message queue: 11
[all …]
|
| /Zephyr-latest/drivers/sensor/nxp/fxos8700/ |
| D | Kconfig | 41 device to the next.
67 bool "Data ready interrupt to INT1 pin"
70 Say Y to route data ready interrupt to INT1 pin. Say N to route to
93 bool "Pulse interrupt to INT1 pin"
95 Say Y to route pulse interrupt to INT1 pin. Say N to route to INT2 pin.
105 bool "Motion interrupt to INT1 pin"
108 Say Y to route motion interrupt to INT1 pin. Say N to route to INT2 pin.
118 bool "Magnetic vector-magnitude interrupt to INT1 pin"
120 Say Y to route magnetic vector-magnitude interrupt to INT1 pin.
121 Say N to route to INT2 pin.
|
| /Zephyr-latest/boards/adi/max32666evkit/doc/ |
| D | index.rst | 17 - Arm Cortex-M4 with FPU Up to 96MHz
29 - Rx Sensitivity: -95dbm; Tx Power Up to +4.5dbm
44 - Up to 50 GPIO
73 - USB 2.0 Micro B to Serial UARTs
76 - Access to the 8 Analog Inputs Through a 0.1in Header
135 | | | | Close | | | Connects I2C0 SCL and SDA 1.5K pullups to VDDIOH. …
142 | | | | Close | | | Connects I2C1 SCL and SDA 1.5K pullups to VDDIOH. …
149 | | | | Close | | | Connects I2C2 SCL and SDA 1.5K pullups to VDDIOH. …
156 | | | | Close | | | Connects LED D2 to P1_14. …
163 | | | | Close | | | Connects LED D3 to P1_15. …
[all …]
|
| /Zephyr-latest/kernel/include/ |
| D | timeout_q.h | 25 static inline void z_init_timeout(struct _timeout *to) in z_init_timeout() argument
27 sys_dnode_init(&to->node); in z_init_timeout()
30 void z_add_timeout(struct _timeout *to, _timeout_func_t fn,
33 int z_abort_timeout(struct _timeout *to);
35 static inline bool z_is_inactive_timeout(const struct _timeout *to) in z_is_inactive_timeout() argument
37 return !sys_dnode_is_linked(&to->node); in z_is_inactive_timeout()
65 #define z_abort_thread_timeout(to) (0)
66 #define z_is_inactive_timeout(to) 1
|
| /Zephyr-latest/doc/project/ |
| D | modifying_contributions.rst | 9 Zephyr contributors and collaborators are encouraged to assist
11 to Zephyr's main branch as part of the original pull requests. The authors
15 There are occasions, however, when a contributor might need to modify patches
20 own pull requests in order to:
23 * get content merged to the project's main branch as part of a larger
26 * a developer pushes to a branch or pull request opened by another
27 contributor in order to:
29 * assist in updating pull requests in order to get the patches merged
30 to the project's main branch
31 * drive stale pull requests to completion so they can be merged
[all …]
|
| /Zephyr-latest/samples/drivers/led/lp5562/ |
| D | README.rst | 5 Control 4 RGB LEDs connected to an LP5562 driver chip.
10 This sample controls 4 LEDs connected to a TI LP5562 driver, using the
13 1. turn on LEDs to be red
14 2. turn on LEDs to be green
15 3. turn on LEDs to be blue
16 4. turn on LEDs to be white
17 5. turn on LEDs to be yellow
18 6. turn on LEDs to be purple
19 7. turn on LEDs to be cyan
20 8. turn on LEDs to be orange
[all …]
|
| /Zephyr-latest/boards/adi/max32675evkit/doc/ |
| D | index.rst | 8 HART modem which enables the bidirectional transfer of digital data over a current loop, to/from
24 - 44.1μA/MHz ACTIVE Mode at 0.9V up to 12MHzCoremark®
25 - 64.5μA/MHz ACTIVE Mode at 1.1V up to 100MHzCoremark
32 - 12 Channels, Assignable to Either ADC
37 - Up to Two I2C
38 - Up to Two UARTs
39 - Up to 23 GPIOs
40 - Up to Five 32-Bit Timers
47 - TRNG Compliant to SP800-90B
49 - Secure Bootloader to Protect IP/Firmware
[all …]
|
| /Zephyr-latest/samples/bluetooth/hci_uart_3wire/ |
| D | README.rst | 5 Expose a Bluetooth controller to another device or CPU over H5:HCI transport.
10 Expose Bluetooth controller support over UART to another device/CPU
36 The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE
37 controller and expose it to Linux's BlueZ. This can be very useful for testing
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
50 For example, to build for the nRF52840 Development Kit:
62 In order to use the HCI UART H:5 controller with QEMU or :ref:`native_sim <native_sim>` you will
63 need to attach it to the Linux Host first. To do so simply build the sample and
64 connect the UART to the Linux machine, and then attach it with this command:
71 Depending on the serial port you are using you will need to modify the
[all …]
|
| /Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/ |
| D | README.rst | 10 This sample is a minimum application to demonstrate basic power management of Standby mode and
14 when LED2 is OFF to enter to Shutdown Mode
15 when LED2 is ON to enter to Standby Mode
16 release the user button to exit from shutdown mode or from shutdown mode.
24 it should support a clock source alternative to Cortex Systick that can be used
39 After flashing, the LED starts to blink.
41 when LED2 is OFF to enter to Shutdown Mode
42 when LED2 is ON to enter to Standby Mode
43 release the user button to exit from shutdown mode or from shutdown mode.
|
| /Zephyr-latest/samples/bluetooth/hci_uart_async/ |
| D | README.rst | 5 Expose a Bluetooth controller to another device or CPU over asynchronous UART.
39 The instructions below show how to use a Nordic nRF5x device as a Zephyr BLE
40 controller and expose it to Linux's BlueZ.
50 For example, to build for the nRF52832 Development Kit:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
63 to attach it to the Linux Host first. To do so simply build the sample and
64 connect the UART to the Linux machine, and then attach it with this command:
71 Depending on the serial port you are using you will need to modify the
72 ``/dev/ttyACM0`` string to point to the serial device your controller is
73 connected to.
[all …]
|
| /Zephyr-latest/samples/basic/blinky_pwm/ |
| D | README.rst | 15 seconds until it returns to 1 Hz, completing a single blinking cycle. This
18 Some PWM hardware cannot set the PWM period to 1 second to achieve the blinking
19 frequency of 1 Hz. This sample calibrates itself to what the hardware supports
26 The board must have an LED connected to a PWM output channel. The PWM
34 No additional wiring is necessary if ``pwm_led0`` refers to hardware that is
35 already connected to an LED on the board.
45 - connect PWM2 (PA0) to an LED
47 - connect PWM2 (PA0) to an LED
49 - connect PWM2 (PA0) to an LED
51 - connect PWM2 (PA0) to an LED
[all …]
|
| /Zephyr-latest/drivers/serial/ |
| D | Kconfig.native_posix | 9 This enables a UART driver for the POSIX ARCH with up to 2 UARTs.
11 to either connect to the terminal from which the executable was run, or into
21 bool "Connect the UART to its own pseudo terminal"
23 Connect this UART to its own pseudoterminal. This is the preferred
24 option for users who want to use Zephyr's shell.
29 bool "Connect the UART to the invoking shell stdin/stdout"
31 Connect this UART to the stdin & stdout of the calling shell/terminal
34 Note that other, non UART messages, will also be printed to the
36 It is strongly discouraged to try to use this option with the new
48 When ``--wait_uart`` is used, writes to the UART will be held until a
[all …]
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 10 * Examples intended to demonstrate core functionality
13 :kconfig:option:`CONFIG_MULTITHREADING` to ``n``. Since this configuration has
15 been limited, there are conditions on what can be expected to work in
18 What Can be Expected to Work
26 * The ability to boot the application to ``main()``
45 :kconfig:option:`CONFIG_SYS_CLOCK_EXISTS` cannot be set to ``n``.
47 What Cannot be Expected to Work
77 expected to work to some degree when :kconfig:option:`CONFIG_MULTITHREADING` is
78 disabled. Subsystems that are not listed here should not be expected to
84 platform is low-impact. Enhancements to add support to existing
[all …]
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 11 The application uses the MQTT protocol to securely send sensor data
12 to a remote MQTT broker, while responding to commands received over MQTT.
17 - Establishing a secure MQTT connection (using TLS 1.2) to MQTT broker
18 - Publishing temperature sensor data in JSON format to the MQTT broker at a user-defined interval
19 - Subscribing to user-defined topic(s) on MQTT broker
20 - Responding to commands received over the network (LED control)
36 For quick sampling/testing, a configuration is provided to connect to a local MQTT broker
41 If using Ethernet, connect the board to the MQTT broker. This may be your host PC
43 (to connect to the public Mosquitto broker).
44 If required, connect a temperature sensor to the board.
[all …]
|
