| /FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_Echo_Qemu_mps2/ |
| A D | syscalls.c | 34 __attribute__( ( used ) ) int _fstat( int file );
35 int _read( int file,
38 int _write( int file,
81 _uart_putc(char c, FILE *file) in _uart_putc() argument
83 ( void ) file; in _uart_putc()
99 int _fstat( int file ) in _fstat() argument
101 ( void ) file; in _fstat()
110 int _read( int file, in _read() argument
114 ( void ) file; in _read()
128 int _write( int file, in _write() argument
[all …]
|
| A D | Readme_UserNetworking.md | 136 -object filter-dump,id=tap_dump,netdev=mynet0,file=/tmp/qemu_tap_dump
148 4. The above QEMU command creates a network packet dump in the file
|
| /FreeRTOS-Plus/VisualStudio_StaticProjects/MbedTLS/ |
| A D | mbedtls_freertos_port.c | 295 int file; in mbedtls_hardware_poll() local
302 file = _open( "/dev/urandom", O_RDONLY ); in mbedtls_hardware_poll()
304 if( file >= 0 ) in mbedtls_hardware_poll()
306 rslt = _read( file, ( char * ) output, len ); in mbedtls_hardware_poll()
324 ( void ) _close( file ); in mbedtls_hardware_poll()
335 FILE * file; in mbedtls_hardware_poll() local
341 file = fopen( "/dev/urandom", "rb" ); in mbedtls_hardware_poll()
343 if( file != NULL ) in mbedtls_hardware_poll()
345 rslt = fread( output, 1, len, file ); in mbedtls_hardware_poll()
346 fclose( file ); in mbedtls_hardware_poll()
|
| /FreeRTOS-Plus/Source/Reliance-Edge/os/freertos/include/ |
| A D | redosdeviations.h | 55 #define PRINT_ASSERT( file, line ) \ argument
56 …printf( "Assertion failed in \"%s\" at line %u\n\r", ( ( file ) == NULL ) ? "" : ( file ), ( unsig…
|
| /FreeRTOS-Plus/Test/FreeRTOS-Plus-TCP/Integration/Full-TCP-Suite/ |
| A D | ReadMe.txt | 2 their own .zip file download, but using the directory structure of the official
3 FreeRTOS .zip file download. This allow the projects to be seamlessly moved
7 The FreeRTOS+TCP test suite Visual Studio project file is in the following
14 - Open the project (using file named `Full-TCP-Suite.sln`) and
17 - Modify the `tcptestECHO_SERVER_ADDR[0-3]` and `tcptestECHO_PORT` in the file
|
| /FreeRTOS-Plus/Test/FreeRTOS-Plus-TCP/Integration/Full-TCP-Networkless/ |
| A D | ReadMe.txt | 2 their own .zip file download, but using the directory structure of the official
3 FreeRTOS .zip file download. This allow the projects to be seamlessly moved
7 The FreeRTOS+TCP Integration Tests Visual Studio project file is in the following
13 Open the project (using file named "FreeRTOS_Plus_TCP_Integration_Tests.sln") and
|
| /FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_IPv6_Demo/IPv6_Multi_WinSim_demo/ |
| A D | ReadMe.md | 24 The FreeRTOS+TCP Multiple Interface Visual Studio project file is
45 1. Set `mainCREATE_TCP_ECHO_TASKS_SINGLE` to 1 in the [main.c](main.c) file.
63 file.
120 file.
135 1. Set `mainCREATE_CLI_TASK` to 1 in the [main.c](main.c) file.
137 `pcCommandList` array in the [main.c](main.c) file. By default,
140 file.
181 [FreeRTOSConfig.h](FreeRTOSConfig.h) file:
194 [FreeRTOSIPConfig.h](FreeRTOSIPConfig.h) file.
200 [UDPEchoClient_SingleTasks.c](UDPEchoClient_SingleTasks.c) file.
[all …]
|
| /FreeRTOS-Plus/Demo/AWS/Ota_Windows_Simulator/ |
| A D | README.md | 3 …k/tree/main) for carrying out over the air updates using MQTT and HTTP protocols for file transfer.
5 …nce demo](https://github.com/FreeRTOS/Lab-Project-ota-example-for-AWS-IoT-Core?tab=readme-ov-file).
|
| /FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_Minimal_Windows_Simulator/ |
| A D | ReadMe.txt | 2 their own .zip file download, but using the directory structure of the official
3 FreeRTOS .zip file download. This allow the projects to be seamlessly moved
7 The minimal FreeRTOS+TCP Visual Studio project file is in the following directory:
34 A description of the way the main FreeRTOS .zip file download source code is
|
| /FreeRTOS-Plus/Source/Reliance-Edge/ |
| A D | README.md | 3 Reliance Edge is a small, portable, highly reliable power-fail safe file system
5 in C and provides a familiar POSIX-like file system API, making it easy to use
37 system failures. Compared to "raw" disk access, using a file system like
39 objects, and allows data to be updated more reliably. Compared to the FAT file
40 system, using Reliance Edge eliminates the possibility that file system data
42 not need a fsck/CHKDSK utility. Compared to journaling file systems, Reliance
46 Reliance Edge uses a unique transactional model that not only prevents file
63 that variety are better served by other file systems, like Datalight's
64 [Reliance Nitro](http://www.datalight.com/products/embedded-file-systems/reliance-nitro).
87 red\_init() or RedFseInit() functions) and then volumes can be mounted and file
[all …]
|
| A D | README.txt | 6 Reliance Edge is a small, portable, highly reliable power-fail safe file
8 It is written in C and provides a familiar POSIX-like file system API,
44 other system failures. Compared to "raw" disk access, using a file
47 Compared to the FAT file system, using Reliance Edge eliminates the
48 possibility that file system data will be left in an inconsistent state,
50 Compared to journaling file systems, Reliance Edge has less overhead and
54 file system corruption but also allows a set of changes to be made in an
72 Embedded systems of that variety are better served by other file
99 mounted and file and directory functions invoked. The Reliance Edge API
135 contributing a significant amount of code, you will be asked to file a
|
| /FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth_wolfSSL/ |
| A D | README_wolfSSL.md | 9 By double-clicking the solution file named "**mqtt_mutual_auth_demo_wolfSSL.sln**" included in this…
11 All required settings for wolfSSL have been set in the user_settings.h header file included in the …
42 For setting those credentials, you have a option to specify the source of them, using file or using…
49 ## Setting credentials using file
53 …ommented out, therefore each credential should be provided by PEM encoded file. In this case, each…
56 #define democonfigROOT_CA_PEM "rootCA-PEM-encoded-file-path"
58 Activate two other macro definitions and set a file path for each.
78 …here..." portion of each macro should be replaced with corrensponding credential file content data.
114 …ailable on the system. Open the **FreeRTOSConfig.h** file in the same folder where this readme fil…
|
| /FreeRTOS-Plus/Source/Application-Protocols/network_transport/ |
| A D | readme.txt | 4 2. Build the wrapper file located in the directory (i.e. sockets_wrapper.c).
|
| A D | transport_mbedtls_pkcs11.h | 222 const char * file,
|
| A D | transport_mbedtls.h | 243 const char * file,
|
| /FreeRTOS-Plus/Source/FreeRTOS-Plus-IO/ |
| A D | readme.txt | 5 a command line interface (using FreeRTOS+CLI) and a FAT file system is
|
| /FreeRTOS-Plus/Test/FreeRTOS-Plus-TCP/Integration/Full-TCP-Suite/WinPCap/ |
| A D | remote-ext.h | 39 … #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
|
| /FreeRTOS-Plus/ThirdParty/winpcap/include/ |
| A D | remote-ext.h | 39 … #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
|
| /FreeRTOS-Plus/Test/FreeRTOS-Cellular-Interface/Integration/WinPCap/ |
| A D | remote-ext.h | 39 … #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
|
| /FreeRTOS-Plus/Test/FreeRTOS-Plus-TCP/Integration/Full-TCP-Networkless/WinPCap/ |
| A D | remote-ext.h | 39 … #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
|
| /FreeRTOS-Plus/Demo/FreeRTOS_Plus_TCP_IPv6_Demo/common/WinPCap/ |
| A D | remote-ext.h | 39 … #error Please do not include this file directly. Just define HAVE_REMOTE and then include pcap.h
|
| /FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Mutual_Auth/ |
| A D | mqtt_broker_setup.txt | 50 10. In the certs folder of your Documents, you will find a file called `ca.crt`.
57 11. In the certs folder of your Documents, you will find a file called `client.crt`.
64 12. In the certs folder of your Documents, you will find a file called `client.key`.
|
| /FreeRTOS-Plus/Source/Reliance-Edge/doc/ |
| A D | release_notes.md | 3 This file contains a list of updates made to Reliance Edge over the course of
39 outdated configuration file is used with Reliance Edge or vice versa.
108 functions used in redconf.h. An existing redconf.h file from v0.9 will need
109 to be updated; for a file containing the old names, the new config tool will
|
| A D | release_notes.txt | 6 This file contains a list of updates made to Reliance Edge over the
47 when an outdated configuration file is used with Reliance Edge or
127 memory functions used in redconf.h. An existing redconf.h file from
128 v0.9 will need to be updated; for a file containing the old names,
|
| /FreeRTOS-Plus/Demo/coreMQTT_Windows_Simulator/MQTT_Multitask/ |
| A D | mqtt_broker_setup.txt | 55 10. In the certs folder of your Documents, you will find a file called `ca.crt`.
62 11. In the certs folder of your Documents, you will find a file called `client.crt`.
69 12. In the certs folder of your Documents, you will find a file called `client.key`.
|