Skip to content

cpu/esp*: Xtensa vendor code moved to esp_common#10883

Merged
smlng merged 13 commits into
RIOT-OS:masterfrom
gschorcht:esp_common_xtensa
Apr 15, 2019
Merged

cpu/esp*: Xtensa vendor code moved to esp_common#10883
smlng merged 13 commits into
RIOT-OS:masterfrom
gschorcht:esp_common_xtensa

Conversation

@gschorcht

@gschorcht gschorcht commented Jan 27, 2019

Copy link
Copy Markdown
Contributor

Contribution description

This PR contains all the changes required to use the same vendor code for context, exception, and interrupt handling for ESP8266 and ESP32.

Testing procedure

tests/thread_basic should still work for an ESP8266 board as well as an ESP32 board.

Issues/PRs references

Depends on #10981
This PR is part of refactoring ESP8266 and ESP32 code in issue #10658.

@gschorcht gschorcht added Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation Platform: ESP Platform: This PR/issue effects ESP-based platforms Area: cpu Area: CPU/MCU ports labels Jan 27, 2019

@smlng smlng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

nice consolidation

Comment thread cpu/esp32/thread_arch.c
@smlng smlng added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Feb 4, 2019

@smlng smlng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

mostly doc-related, i.e. use @name for groups instead of @brief ... though this was overseen when merging the original code.

Comment thread cpu/esp32/include/irq_arch.h Outdated
Comment thread cpu/esp32/include/irq_arch.h Outdated
Comment thread cpu/esp32/include/irq_arch.h Outdated
@gschorcht

Copy link
Copy Markdown
Contributor Author

@smlng Changed.

@gschorcht

Copy link
Copy Markdown
Contributor Author

@smlng Too late for the 2019.04 release but not too late for next release 😄 I would like to make some progress with this PR (as well as with #10929) since these PRs provide important improvements that are prerequisites for the reimplementation of ESP8266 port in PR #11108.

Sorry that I'm pushing a bit 😎 but the conflicts with current master in PR #11108 are already increasing a lot. It will become more and more difficult to resolve all these conflicts while guaranteeing that the reimplementation PR #11108 keeps as stable as it already was. It was already tested completely.

@smlng smlng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

tested ACK!

@smlng smlng added Reviewed: 1-fundamentals The fundamentals of the PR were reviewed according to the maintainer guidelines Reviewed: 2-code-design The code design of the PR was reviewed according to the maintainer guidelines Reviewed: 3-testing The PR was tested according to the maintainer guidelines Reviewed: 4-code-style The adherence to coding conventions by the PR were reviewed according to the maintainer guidelines Reviewed: 5-documentation The documentation details of the PR were reviewed according to the maintainer guidelines labels Apr 15, 2019
@smlng

smlng commented Apr 15, 2019

Copy link
Copy Markdown
Member

please rebase and squash as needed

@gschorcht

Copy link
Copy Markdown
Contributor Author

@sming Thanks for reviewing and testing it again. Rebased and squashed.

@smlng

smlng commented Apr 15, 2019

Copy link
Copy Markdown
Member

Side note: careful with my GitHub name, its smlng with lower case L not i, i.e. no vowels. The other guy (sming) already got annoyed a couple times 😬

@smlng

smlng commented Apr 15, 2019

Copy link
Copy Markdown
Member

CI is not happy, some whitespace stuff, please amend fix directly

@gschorcht

Copy link
Copy Markdown
Contributor Author

Side note: careful with my GitHub name, its smlng with lower case L not i, i.e. no vowels. The other guy (sming) already got annoyed a couple times

Ups 😎 Usually, I only type in 'sm' and use the completion which is usually 'smlng'. I didn't take much care. I thought Github is intelligent enough to know from the context of the PR that I didn't want to refer 'sming'.

Usually, the access to the IROM (flash) memory requires 32-bit word aligned reads. Attempts to access data in the IROM (flash) memory less than 32 bits in size triggers a LoadStoreError exception. With the exception handler from esp-open-rtos it becomes possible to access data in IROM (flash) with a size of less than 32 bits and thus to place .rodata sections in the IROM (flash).
@gschorcht

Copy link
Copy Markdown
Contributor Author

@smlng Fixed and all light are green.

@smlng

smlng commented Apr 15, 2019

Copy link
Copy Markdown
Member

retested, all good!

@smlng smlng merged commit 35c617e into RIOT-OS:master Apr 15, 2019
@gschorcht gschorcht deleted the esp_common_xtensa branch April 15, 2019 11:30
@gschorcht

Copy link
Copy Markdown
Contributor Author

@smlng Thanks again for your fast support.

@smlng

smlng commented Apr 15, 2019

Copy link
Copy Markdown
Member

@smlng Thanks again for your fast support.

Sure thing. I now have a couple of ESP lying around at work and home, so I'm happy to help where ever I can to keep the RIOT support for ESP up and running (and improving)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: cpu Area: CPU/MCU ports CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Platform: ESP Platform: This PR/issue effects ESP-based platforms Reviewed: 1-fundamentals The fundamentals of the PR were reviewed according to the maintainer guidelines Reviewed: 2-code-design The code design of the PR was reviewed according to the maintainer guidelines Reviewed: 3-testing The PR was tested according to the maintainer guidelines Reviewed: 4-code-style The adherence to coding conventions by the PR were reviewed according to the maintainer guidelines Reviewed: 5-documentation The documentation details of the PR were reviewed according to the maintainer guidelines Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants