Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zephyr federated project #3

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Conversation

siljesu
Copy link

@siljesu siljesu commented Jun 3, 2023

Additions:

  • New structure in Applications-folder
  • Two new custom west commands, lf-fed-build and lf-fed-flash. See README for documentation of use.
  • Updated README with federated
  • Three federated applications with configuration files
  • Updated .gitignore

@lhstrh lhstrh requested a review from erlingrj June 3, 2023 19:40
Copy link
Collaborator

@erlingrj erlingrj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work Silje! But would like to iterate a few times over the west extensions. Each West extension should also be in a separate Python file.

Comment on lines +1 to +6
application/*/src-gen
application/*/fed-gen
application/*/bin
application/*/build
application/*/include
application/*/*build/**
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
application/*/src-gen
application/*/fed-gen
application/*/bin
application/*/build
application/*/include
application/*/*build/**
**/src-gen
**/fed-gen
**/bin
**/build
**/include

Comment on lines +8 to +15
&{/leds} {
compatible = "gpio-leds";
led-2 {
gpios = < &gpio9 0x19 GPIO_ACTIVE_HIGH >;
label = "User LED D34, GPIO9 AD 26";
status = "okay";
};
};
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isnt this part of the DTS of the dev-kit?

Comment on lines +17 to +20
&enet {
local-mac-address = [00 0a 35 00 00 02];
status = "okay";
};
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you have any idea how this is done for other boards? Do you have a link to where you found info about this?

# Network application options and configuration
CONFIG_NET_CONFIG_SETTINGS=y
CONFIG_NET_CONFIG_NEED_IPV4=y
CONFIG_NET_CONFIG_MY_IPV4_ADDR="192.0.2.3"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems all parameters except this one, is common for both. Could they be extracted in a single common config file?

exit(1)

class LfFedBuild(WestCommand):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command seems to copy-and-paste a lot from the other build command. Would it be possible to combine them into a single command with additional options for building federates? Or, could we use the other lf-build command within this one?

exit(1)

class LfFedFlash(WestCommand):
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This command is very NXP EVK specific as it is using one particular flash/debug tool (pyOCD). As it is, I think it should be renamed to flash-evk or something. Alternatively we should look into how to make it more board independent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants