profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/alexkalmuk/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

embox/embox 663

Modular and configurable OS for embedded applications

embox/pjsip 7

Scripts for building pjsip environment for host machine

AntonKozlov/fault-car 1

fault-car support repo

alexkalmuk/CppCoreGuidelines 0

The C++ Core Guidelines are a set of tried-and-true guidelines, rules, and best practices about coding in C++

alexkalmuk/emdocker 0

Docker build and test environment

alexkalmuk/emdocker-test 0

Docker image for testing utils

alexkalmuk/fuse-ext2 0

Fuse-ext2 is a multi OS FUSE module to mount ext2, ext3 and ext4 file system devices and/or images with read write support.

issue closedOpenEtherCATsociety/SOEM

Source MAC address compliance with Ethernet standard

This is more out of curiosity. In Wireshark, I get the following warning:

[Source MAC must not be a group address: IEEE 802.3-2002, Section 3.2.3(b)]

It's because 01:01:01:01:01:01 (multicast) is used as the source MAC address.

From oshw/linux/nicdrv.c:

/** Primary source MAC address used for EtherCAT.
 * This address is not the MAC address used from the NIC.
 * EtherCAT does not care about MAC addressing, but it is used here to
 * differentiate the route the packet traverses through the EtherCAT
 * segment. This is needed to find out the packet flow in redundant
 * configurations. */
const uint16 priMAC[3] = { 0x0101, 0x0101, 0x0101 };
/** Secondary source MAC address used for EtherCAT. */
const uint16 secMAC[3] = { 0x0404, 0x0404, 0x0404 };

Is there any reason to do not comply with Ethernet standard here for priMAC? What if the master is connected to an ethernet switch, for example? Probably it's better to fix priMAC to something like secMAC - 0a:0a:0a:0a:0a:0a.

closed time in a month

alexkalmuk

issue commentOpenEtherCATsociety/SOEM

Source MAC address compliance with Ethernet standard

I'm sorry to bother you. Thank you!

alexkalmuk

comment created time in a month

issue openedOpenEtherCATsociety/SOEM

Source MAC address compliance with Ethernet standard

This is more out of curiosity. In Wireshark, I get the following warning:

[Source MAC must not be a group address: IEEE 802.3-2002, Section 3.2.3(b)]

It's because 01:01:01:01:01:01 (multicast) is used as the source MAC address.

From oshw/linux/nicdrv.c:

/** Primary source MAC address used for EtherCAT.
 * This address is not the MAC address used from the NIC.
 * EtherCAT does not care about MAC addressing, but it is used here to
 * differentiate the route the packet traverses through the EtherCAT
 * segment. This is needed to find out the packet flow in redundant
 * configurations. */
const uint16 priMAC[3] = { 0x0101, 0x0101, 0x0101 };
/** Secondary source MAC address used for EtherCAT. */
const uint16 secMAC[3] = { 0x0404, 0x0404, 0x0404 };

Is there any reason to do not comply with Ethernet standard here for priMAC? What if the master is connected to an ethernet switch, for example? Probably it's better to fix priMAC to something like secMAC - 0a:0a:0a:0a:0a:0a.

created time in a month

PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent
PullRequestReviewEvent

push eventembox/embox

Alex Kalmuk

commit sha 4d9f87046941b7345e4d2cbef64868bdc13e50fa

scripts: Fix scripts/gdb_run_stm32h7_qspi.sh

view details

Alex Kalmuk

commit sha 1f0695ed5f4b3350e8d49ebe446624020e599baa

scripts: Add rom erasing script gdb_erase_stm32h7.sh

view details

Alex Kalmuk

commit sha ce9bc63bd342890cdbfd80a4cc743f3879f112bb

Merge pull request #2465 from embox/stm32h7-qspi Stm32h7 qspi flashing

view details

push time in 3 months

PR merged embox/embox

Stm32h7 qspi flashing
+28 -6

0 comment

2 changed files

alexkalmuk

pr closed time in 3 months

PR opened embox/embox

Stm32h7 qspi flashing
+28 -6

0 comment

2 changed files

pr created time in 3 months

create barnchembox/embox

branch : stm32h7-qspi

created branch time in 3 months

PullRequestReviewEvent
PullRequestReviewEvent