Home
last modified time | relevance | path

Searched refs:a (Results 1 – 25 of 122) sorted by relevance

12345

/FreeRTOS-Plus-TCP-v4.0.0/
DHistory.txt22 + Stack is Penetration tested and a memory leak issue has been identified and fixed in the process.
71 + Fixed a bug in the Connect function where multiple SYN and RST packet combinations can
87 + Added a check in BufferAllocation_2.c to ensure adding (2 +
97 + Added logic to clear flags of a stored TCP packet to avoid
103 + When a listening socket is closed, all child sockets not yet owned by the
105 + Updated buffer allocation to return a zero length buffer when
107 + When there is insufficient space in the network event queue, closing of a
108 socket will be deferred for a later time. (Thanks Bernd Edlinger).
113 + Added a hook function which can be used to process unsupported ethernet
115 + Added a check for ICMP packets with incorrect checksum.
[all …]
DMISRA.md5 Since the FreeRTOS-Plus-TCP library is designed for small-embedded devices, it needs to have a very…
37 Thus, it marks some statements as dead code. This is a false positive.
52 However, the FreeRTOS-kernel function `xTaskCreate` expects a function signature
54 function signature of `prvIPTask` does not have a `const` qualifier in the
61 operation is safe to perform in that case, as we are using a generic API
67 - MISRA C-2012 Rule 11.1 Converting from a void pointer to a function pointer.
78 - MISRA C-2012 Rule 11.3 The data received/sent by the IP stack is represent as a
81 a byte stream to a structure, MISRA warns us that it can lead to
83 packets are stored are always aligned to a 4 byte word boundary with an
89 instead of a `uint32_t`.
[all …]
DREADME.md7 FreeRTOS-Plus-TCP is a lightweight TCP/IP stack for FreeRTOS. It provides a familiar Berkeley socke…
13 …RTOS source files included, and the correct include paths configured. Once a demo application is …
20 …e the [Submitting a bugs/feature request](https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/blob/main/…
25 …security vulnerabilities. Additionally, the source files have been moved to a `source` directory. …
30 If you wish to continue using a version earlier than V3.0.0 i.e. continue to use your existing sour…
32 …ot pose any problems to most projects as projects generally include all files in a given directory.
46 Add the following into your project's main or a subdirectory's `CMakeLists.txt`:
59 - this particular example supports a native and cross-compiled build option.
78 … you will not get the contents of the submodules. (The ZIP file is also not a valid Git repository)
97 This repository contains the FreeRTOS-Plus-TCP repository and a number of supplementary libraries f…
[all …]
/FreeRTOS-Plus-TCP-v4.0.0/.github/
DCONTRIBUTING.md3 Thank you for your interest in contributing to our project. Whether it's a bug report, new feature,…
15 …a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vul…
18 ## Submitting a bugs/feature request
19 Have a bug to report or feature to request? Follow these steps:
21 2. If your search turns up empty, create a new topic in the [forums](https://forums.freertos.org/) …
24 When creating a new topic on the forums or filing an issue, please include as many relevant details…
34 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensu…
40 To send us a pull request, please:
46 5. Send us a pull request, answering any default questions in the pull request interface.
50 GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork…
[all …]
DSECURITY.md1 ## Reporting a Vulnerability
3 If you discover a potential security issue in this project we ask that you notify AWS/Amazon Securi…
5 Please do **NOT** create a public github issue.
DCODEOWNERS1 # Each line is a file pattern followed by one or more owners.
4 # the repo. Unless a later match takes precedence,
6 # review when someone opens a pull request.
10 # precedence. When someone opens a pull request that only
12 # owner(s) will be requested for a review.
/FreeRTOS-Plus-TCP-v4.0.0/docs/doxygen/
Dstyle.css10 /* Set the margins to place a small amount of whitespace on the left and right
89 /* Style of paragraphs on a configuration settings page. */
123 color: #50015a;
130 a.code, a.code:visited, a.line, a.line:visited {
Dconfig.doxyfile4 # doxygen (www.doxygen.org) for a project.
6 # All text after a double hash (##) is considered a comment and is placed in
9 # All text after a single hash (#) is considered a comment and will be ignored.
39 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by
42 # title of most generated pages and in a few other places.
47 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
54 # for a project that appears at the top of each page and should give viewer a
59 # With the PROJECT_LOGO tag one can specify a logo or an icon that is included
67 # into which the generated documentation will be written. If a relative path is
76 # option can be useful when feeding doxygen a huge amount of source files, where
[all …]
/FreeRTOS-Plus-TCP-v4.0.0/test/cbmc/proofs/DHCP/DHCPProcessEndPoint/
DREADME.md5 that the buffer is large enough to accomodate a DHCP message plus a
7 field in a DHCP message). We have abstracted away sockets, concurrency
11 This proof is a work-in-progress. Proof assumptions are described in
/FreeRTOS-Plus-TCP-v4.0.0/source/
DFreeRTOS_IP_Utils.c1579 int32_t FreeRTOS_max_int32( int32_t a, in FreeRTOS_max_int32() argument
1582 return ( a >= b ) ? a : b; in FreeRTOS_max_int32()
1592 uint32_t FreeRTOS_max_uint32( uint32_t a, in FreeRTOS_max_uint32() argument
1595 return ( a >= b ) ? a : b; in FreeRTOS_max_uint32()
1605 size_t FreeRTOS_max_size_t( size_t a, in FreeRTOS_max_size_t() argument
1608 return ( a >= b ) ? a : b; in FreeRTOS_max_size_t()
1618 int32_t FreeRTOS_min_int32( int32_t a, in FreeRTOS_min_int32() argument
1621 return ( a <= b ) ? a : b; in FreeRTOS_min_int32()
1631 uint32_t FreeRTOS_min_uint32( uint32_t a, in FreeRTOS_min_uint32() argument
1634 return ( a <= b ) ? a : b; in FreeRTOS_min_uint32()
[all …]
/FreeRTOS-Plus-TCP-v4.0.0/source/include/
DFreeRTOS_IP.h251 int32_t FreeRTOS_max_int32( int32_t a,
254 uint32_t FreeRTOS_max_uint32( uint32_t a,
257 size_t FreeRTOS_max_size_t( size_t a,
260 int32_t FreeRTOS_min_int32( int32_t a,
263 uint32_t FreeRTOS_min_uint32( uint32_t a,
266 size_t FreeRTOS_min_size_t( size_t a,
269 uint32_t FreeRTOS_round_up( uint32_t a,
271 uint32_t FreeRTOS_round_down( uint32_t a,
/FreeRTOS-Plus-TCP-v4.0.0/test/Coverity/
DREADME.md4 To that end, this directory provides a [CMake](https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/blob/m…
16 You can run this on a platform supported by Coverity. The list and other details can be found [here…
33 2. Create the build files using CMake in a `build` directory
56 You should now have the HTML formatted violations list in a directory named `html-output`.
59 This deviation has a justification outlined [here](https://github.com/FreeRTOS/FreeRTOS-Plus-TCP/bl…
60 that justification in place, a coverity suppression statement has been added to the code. However, …
62 the HTML formatted report. If you find a way around it, please help us fix this by creating a pull-…
DCMakeLists.txt19 …message( FATAL_ERROR "In-source build is not allowed. Please build in a separate directory, such a…
37 # Add kernel sources to a list
41 # Add TCP sources to a list
45 # A better way would be to create a library such that all other dependencies are
/FreeRTOS-Plus-TCP-v4.0.0/source/portable/NetworkInterface/ThirdParty/MSP432/
DREADME.md14 This is a driver and network middleware for the MSP432E401Y microcontroller
23 When a MAC address changes or when there is a change in the network setup,
24 it is recommended to perform a hard reset of the microcontroller in lieu
56 config.MACAddr[0] = 0x70; /* replace with a custom MAC address */
69 … network task to reset the network every so often (i.e. to periodically obtain a new IP address) */
80 … Use publicPreventNetworkReset() to block the network reset during a critical section of the code
/FreeRTOS-Plus-TCP-v4.0.0/source/portable/NetworkInterface/STM32Hxx/
Dreadme.md8 The descriptors for transmission are protected with a counting semaphore.
9 By the time that a packet has been sent, the other TX descriptor becomes
17 Here are settings give a high performance for iperf3:
57 Here is a table of 3 types of STH32H7 :
71 If you use a memory that is not supported, it will result in a DMA errors.
73 Don't redefine a new memory area (like AXI-SRAM, RAM_D1) if it already exists in the
92 The copy-method also works well, may just a little slower.
126 FreeRTOS+TCP never uses this feature. Each packet is stored in a single buffer called
/FreeRTOS-Plus-TCP-v4.0.0/tools/tcp_utilities/
Dtcp_dump_packets.md1 tcp_dump_packets.c dumps network packets in a C source file.
8 How to include 'tcp_dump_packets' into a project:
14 ● Once the network is up, call `dump_packet_init()` with a file name and a pointer to
54 Each property is defined as a bit so they can be combined as in:
/FreeRTOS-Plus-TCP-v4.0.0/source/portable/NetworkInterface/STM32Fxx/
Dreadme.md1 This is a FreeeRTOS+TCP driver that works for STM32Fxx parts.
30 Choose a proper interrupt priority, defined in FreeRTOSIPConfig.h as e.g. :
37 and not a dummy defined as "weak".
100 When MTU is 1500, MTU+36 becomes a well-aligned buffer of 1536 bytes ( 0x600 ).
106 Without memory caching, let the size be at least a multiple of 8 ( for DMA ), and make it at least …
110 NetworkInterface.c will place the 2 DMA tables in a special section called 'first_data'.
120 _sdata = .; // create a global symbol at data start
126 _edata = .; // define a global symbol at data end
/FreeRTOS-Plus-TCP-v4.0.0/test/cbmc/proofs/ARP/ARP_FreeRTOS_OutputARPRequest/
DREADME.md3 This proof is a work-in-progress. Proof assumptions are described in
13 guarantees that for a buffer allocated to xDataLength,
18 a buffer of at least ipconfigETHERNET_MINIMUM_PACKET_BYTES,
/FreeRTOS-Plus-TCP-v4.0.0/test/cbmc/
DREADME.md13 how to run the proofs on your local clone of a:FR.
20 and CTest. Others use a custom python-based build system. New proofs
110 If you are on a Windows machine but want to generate Linux Makefiles (or vice
117 Each of the leaf directories under `proofs` is a proof of the memory
118 safety of a single entry point in FreeRTOS. The scripts that you ran in the
119 previous step will have left a Makefile in each of those directories. To
120 run a proof, change into the directory for that proof and run `nmake` on
131 - `patches` contains a set of patches that get applied to the codebase prior to
/FreeRTOS-Plus-TCP-v4.0.0/test/unit-test/FreeRTOS_IP_Utils_DiffConfig/
DFreeRTOS_IP_Utils_DiffConfig_utest.c129 uint32_t a = 10; in test_FreeRTOS_round_up() local
131 ulReturn = FreeRTOS_round_up( a, 0 ); in test_FreeRTOS_round_up()
143 uint32_t a = 10; in test_FreeRTOS_round_down() local
145 ulReturn = FreeRTOS_round_down( a, 0 ); in test_FreeRTOS_round_down()
/FreeRTOS-Plus-TCP-v4.0.0/test/cbmc/proofs/IP/SendEventToIPTask/
DREADME.md1 This is the memory safety proof for xSendEventToIPTask, a function used
4 This proof is a work-in-progress. Proof assumptions are described in
/FreeRTOS-Plus-TCP-v4.0.0/source/portable/NetworkInterface/board_family/
DReadMe.txt3 …is Not! to be used as is. The purpose of the file is to provide a template for writing a network i…
/FreeRTOS-Plus-TCP-v4.0.0/source/portable/NetworkInterface/
DREADME_DRIVER_DISCLAIMER.txt7 + May have a dependency on a particular PHY part number.
/FreeRTOS-Plus-TCP-v4.0.0/test/cbmc/include/
Dcbmc.h30 #define IMPLIES( a, b ) ( !( a ) || ( b ) ) argument
/FreeRTOS-Plus-TCP-v4.0.0/.github/ISSUE_TEMPLATE/
Dbug_report.md3 about: Create a report to help us improve FreeRTOS-Plus-TCP. This should only be used
13 … proprietary, please upload the code in a [GitHub fork](https://docs.github.com/en/get-started/qui…

12345