EEPROM | The official EEPROM library used by the Arduino IDE

1. In a text stream, the new-line character is translated. Some operating systems translated to \r\n. A binary stream leaves it as it is.

2. Regardless of how you opened the stream – binary or text:

   a. When you use the insertion/extraction operator the data is written as text. Assuming 0x01 is a one byte integer, ASCII 1 will be written (that is 0x31).

   b. If you use the ostream::write method, you write the actual bytes; no translations happens. Assuming 0x01 is a one byte integer, 0x01 will be written.

3. If you want to write the actual bytes, open the stream in binary mode and use ostream::write:

Support for GRE and/or Inner RSS is touch and go for many NIC, so most NIC does not work out of box. For example

1. For Intel Fortville (10gbps, 25Gbps, 40Gbps) NIC: one needs to update firmware and DDP profile to parse and compute inner RSS.
2. For Intel Columbiaville (100Gbps, 50Gbps, 25Gbps) NIC: one needs to update firmware and then update driver. As I recollect default DDP profile parses GRE.
3. In case of Mellanox MLX5 (there are multiple variant for ConnectX-5 and Connect-6), some of them support GRE based parsing and RSS, while other require ESWITCH to perform such actions.

Hence using testpmd one needs to

1. enable MQ_RSS in port and RX queue configuration
2. For specific (inner RSS) enable via RTE_FLOW API

With MT2892 Family [ConnectX-6 Dx] one can enable Inner 5 tuple RSS for GRE encapsulated packet with testpmd.

1. Start packet generator (DPDK pktgen) use sudo ./usr/local/bin/pktgen --file-prefix=3 -a81:00.0,txq_inline_mpw=128 -l 6-27 -- -P -m "[8-11:12-27].0" -N -s"0:rtp_balanced_gre.pcap"
2. Start testpmd in interactive mode with multiple RX queues using dpdk-testpmd --socket-mem=1024 --file-prefix=2 -l 7,8-23 -a0000:41:00.1,mprq_en=1,rxqs_min_mprq=1,mprq_log_stride_num=9,txq_inline_mpw=128,rxq_pkt_pad_en=1,rxq_cqe_comp_en=4 -- --port-numa-config=0,0 --socket-num=0 --burst=128 --txd=8192 --rxd=8192 --mbcache=512 --rxq=16 --txq=16 --nb-cores=8 -a --forward-mode=io --numa --rss-udp --enable-rx-cksum --no-mlockall --no-lsc-interrupt -a --enable-rx-cksum --enable-drop-en --eth-link-speed=100000 --no-rmv-interrupt -i
3. In interactive shell configure the rule as flow create 0 ingress pattern eth / ipv4 / gre / eth / ipv4 / udp / end actions rss level 2 types ip udp end queues 0 1 2 3 end / end.

Note:

1. Ensure to use the right format in match field eth / ipv4 / gre / eth / ipv4 / udp /
2. if the rule is not set on the device only device RX queue0 will be receiving the packets.

If you want the script to be executed by bash as the shebang line dictates then do

SOLVED! Turned out (after a few sleepless nights) that

You can have a look into the GlobalPlatform project loader. It is LPGL, so directly using it as C code in other non LGPL projects is not possible.

[!!!!] LOAD - Method (FAILED)

80e800057007006d000911188c00048d00012c18197b0002037b00029210240303038b000388007a02318f00053d8c00062e1b8b00077a0120188b000860037a7a02228d00092d1d10076b101a8b000a321fae006b06188c000b7a06118d000c2c1903077b000d037b000d928b000e198b000f3b7a00c0000000

<< 9000 (should be 009000)

I assume that the log is the unwrapped logged before the commands are prepared for SCP80. A response of 9000 in OTA means usually "I received the command, but I don't know what to do with it". Is this 9000 command from the ENVELOPE response on the card? Are you sending the data over an SMPP connection?

Can you try your loading code with a simple HelloWorld Applet without any STK? It could be that your card is not supporting a version you are linking against, e.g. different ETSI releases. Then some method might not be supported and the loading fails.

Yes, you are looking for the -P flag, it needs the path to the serial device of the AVR when it's in its bootloader. As long as it is a normal itsybitsy, and not one that's been modified to work without the bootloader, you need to get it into the bootloader by hitting the reset button twice withing 750ms, and within 8 seconds you need to run the avrdude command.

For the -P flag, you posted your dmesg output, and it's the same as my machine, /dev/ttyACM0.

So, my dance to get mine is to hold reset for a count of 5 (to let Linux notice it's gone and free the device it was assigned), hit the reset button again quickly, wait for a second (but not too long; Linux needs to reallocate the tty but you cannot miss the bootloader window), then run the avrdude command:

Some help on can or socketCAN will be found here for the BBB or other family board:

When I did load-testing, I found performance is average and after 200kpps packet rate I noticed packet drops. In short DPDK host hit high PMD cpu usage and loadtest showing bad audio quality. when i do same test with SRI

[Answer] this observation is not true based on the live debug done so far. The reason as stated below

1. qemu launched were not pinned to specific cores.
2. comparison done against PCIe pass-through (VF) against vhost-client is not apples to apples comparison.
3. with OpenStack approach, there are at least 3 bridges before the packets to flow through before reaching VM.
4. OVS threads were not pinned which led to all the PMD threads running on the same core (causing latency and drops) in each bridge stage.

To have a fair comparison against SRIOV approach, the following changes have been made with respect to similar question

The latest release of WiFiManager library (0.16) is almost a year old and doesn't support ESP32.
You will need to install the library from Github to get ESP32 support.

In your platformio.ini replace