Skip to content

ESP8266: treats reset-ready-message as OOB #9473

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

Merged
merged 6 commits into from
Feb 15, 2019
Merged

ESP8266: treats reset-ready-message as OOB #9473

merged 6 commits into from
Feb 15, 2019

Conversation

VeijoPesonen
Copy link
Contributor

@VeijoPesonen VeijoPesonen commented Jan 23, 2019

Description

Makes possible to detect if modem gets reset by handling the reset-ready-message as OOB.

Fixes the network status update callback to not report a state change if a state change hasn't really occurred.

Prevent's running reset twice in a row if reset pin is connected to a known pin.

Fixes UART HW flow control enabling sequence - adds also mutex.

Pull request type

[X] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@SeppoTakalo
@michalpasztamobica
@kjbracey-arm

@ciarmcom
Copy link
Member

@VeijoPesonen, thank you for your changes.
@SeppoTakalo @kjbracey-arm @michalpasztamobica @ARMmbed/mbed-os-ipcore @ARMmbed/mbed-os-maintainers please review.

@cmonr
Copy link
Contributor

cmonr commented Jan 29, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Jan 30, 2019

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 1
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_dynamic-memory-usage

@cmonr
Copy link
Contributor

cmonr commented Jan 30, 2019

Restarted CI job: jenkins-ci/mbed-os-ci_dynamic-memory-usage

The wifi test failed, but it's not clear why.

@VeijoPesonen
Copy link
Contributor Author

VeijoPesonen commented Jan 30, 2019

@cmonr Rebased.

@cmonr
Copy link
Contributor

cmonr commented Jan 31, 2019

CI started

@mbed-ci
Copy link

mbed-ci commented Jan 31, 2019

Test run: FAILED

Summary: 1 of 12 test jobs failed
Build number : 2
Build artifacts

Failed test jobs:

  • jenkins-ci/mbed-os-ci_dynamic-memory-usage

@0xc0170
Copy link
Contributor

0xc0170 commented Jan 31, 2019

Restarted dynamic usage, but still can you check the artifacts to confirm the failure not related?

@VeijoPesonen
Copy link
Contributor Author

Need to admit that the test results doesn't tell me much

[1548944538.40][HTST][INF] host test detected: default_auto
[1548944548.45][CONN][INF] found KV pair in stream: {{max_heap_usage;720}}, queued...
[1548944548.45][CONN][INF] found KV pair in stream: {{reserved_heap;183360}}, queued...
[1548944548.45][HTST][ERR] orphan event in main phase: {{max_heap_usage;720}}, timestamp=1548944548.451403
[1548944548.45][HTST][ERR] orphan event in main phase: {{reserved_heap;183360}}, timestamp=1548944548.451410
[1548944548.55][CONN][INF] found KV pair in stream: {{__thread_info;"0x020001738",1160,4096}}, queued...
[1548944548.55][CONN][INF] found KV pair in stream: {{__thread_info;"0x020001888",80,512}}, queued...
[1548944548.55][HTST][ERR] orphan event in main phase: {{__thread_info;"0x020001738",1160,4096}}, timestamp=1548944548.551406
[1548944548.55][CONN][INF] found KV pair in stream: {{__thread_info;"0x0200008ac",224,2048}}, queued...
[1548944548.55][HTST][ERR] orphan event in main phase: {{__thread_info;"0x020001888",80,512}}, timestamp=1548944548.551413
[1548944548.55][HTST][ERR] orphan event in main phase: {{__thread_info;"0x0200008ac",224,2048}}, timestamp=1548944548.551416
[1548944548.65][CONN][INF] found KV pair in stream: {{__thread_info;"0x020001844",104,768}}, queued...
[1548944548.65][CONN][INF] found KV pair in stream: {{end;failure}}, queued...
[1548944548.65][CONN][INF] found KV pair in stream: {{__exit;0}}, queued...
[1548944548.65][HTST][ERR] orphan event in main phase: {{__thread_info;"0x020001844",104,768}}, timestamp=1548944548.652407
[1548944548.65][HTST][INF] __exit(0)
[1548944548.65][HTST][INF] __notify_complete(False)
[1548944548.65][HTST][INF] __exit_event_queue received
[1548944548.65][HTST][INF] test suite run finished after 10.35 sec...
[1548944548.65][CONN][INF] received special event '__host_test_finished' value='True', finishing
[1548944548.65][urllib3.connectionpool]Starting new HTTP connection (1): ronja.mbedcloudtesting.com:80
[1548944548.87][urllib3.connectionpool]http://ronja.mbedcloudtesting.com:80 "PUT /resource/0311000040214e45003e1018c89200559e11000097969900/disconnect HTTP/1.1" 200 87
[1548944548.88][urllib3.connectionpool]Starting new HTTP connection (1): ronja.mbedcloudtesting.com:80
[1548944552.15][urllib3.connectionpool]http://ronja.mbedcloudtesting.com:80 "PUT /resource/0311000040214e45003e1018c89200559e11000097969900/release HTTP/1.1" 200 87
[1548944552.15][HTST][INF] CONN exited with code: 0
[1548944552.15][HTST][INF] Some events in queue
[1548944552.15][HTST][INF] stopped consuming events
[1548944552.15][HTST][INF] host test result() call skipped, received: False
[1548944552.15][HTST][INF] calling blocking teardown()
[1548944552.15][HTST][INF] teardown() finished
[1548944552.15][HTST][INF] {{result;failure}}
mbedgt: retry mbedhtrun 1/1
mbedgt: ['mbedhtrun', '-m', 'K66F', '-p', 'DUMMY:9600', '-f', u'"BUILD/dynamic/K66F/GCC_ARM/wifi/wifi.bin"', '--grm', 'raas_client:ronja.mbedcloudtesting.com:80', '-C', '4', '--sync', '5', '--tag-filters', 'MEMORY', '-P', '600'] failed after 1 count
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'FAIL'
mbedgt: test case summary event not found
	no test case report present, assuming test suite to be a single test case!
	test suite: wifi
	test case: wifi
mbedgt: test on hardware with target id: DUMMY
mbedgt: test suite 'wifi' ............................................................................ FAIL in 41.72 sec
	test case: 'wifi' ............................................................................ FAIL in 41.72 sec

@cmonr
Copy link
Contributor

cmonr commented Jan 31, 2019

@ARMmbed/mbed-os-test-team Can you help out with this one? Not sure why jenkins-ci/dynamic-memory-usage has repeatedly failed.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 1, 2019

@VeijoPesonen to unblock this, can you talk to @timurh01 ?

@VeijoPesonen
Copy link
Contributor Author

@0xc0170 I'll run the test manually to see what is wrong.

@VeijoPesonen
Copy link
Contributor Author

This requires some further investigation from me as I get same results with manual testing, but once I switch to NRF52840_DK(with ESP8266) - which I used to create this PR - test is passing.

mbedgt: test on hardware with target id: 110200004420312043574641323034203830303697969903
mbedgt: test suite 'wifi' ............................................................................ OK in 64.30 sec
        test case: 'wifi' ............................................................................ OK in 64.30 sec
mbedgt: test case summary: 1 pass, 0 failures
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.4552342797
mbedgt: exporting to JSON 'greentea-report.json'...
mbedgt: exporting memory metrics to CSV file 'memory_usage_temp.csv'...
mbedgt: test suite report:
| target              | platform_name | test suite | result | elapsed_time (sec) | copy_method |
|---------------------|---------------|------------|--------|--------------------|-------------|
| GCC_ARM-NRF52840_DK | NRF52840_DK   | wifi       | OK     | 64.3               | default     |
mbedgt: test suite results: 1 OK
mbedgt: test case report:
| target              | platform_name | test suite | test case | passed | failed | result | elapsed_time (sec) |
|---------------------|---------------|------------|-----------|--------|--------|--------|--------------------|
| GCC_ARM-NRF52840_DK | NRF52840_DK   | wifi       | wifi      | 1      | 0      | OK     | 64.3               |
mbedgt: test case results: 1 OK
mbedgt: completed in 66.81 sec
apps : ['wifi'] memmap ; ['.../mbed-os-benchmarks/BUILD/static/NRF52840_DK/GCC_ARM/wifi/wifi_map.json']

@VeijoPesonen
Copy link
Contributor Author

Ended up being a bit more changes than I anticipated. @SeppoTakalo , @michalpasztamobica please re-review.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 13, 2019

Any update @VeijoPesonen ?

@VeijoPesonen
Copy link
Contributor Author

@0xc0170 depends from ARMmbed/mbed-os-benchmarks#24

@cmonr
Copy link
Contributor

cmonr commented Feb 13, 2019

@VeijoPesonen ARMmbed/mbed-os-benchmarks#24 was just merged. It should now be in use within CI.

@cmonr
Copy link
Contributor

cmonr commented Feb 13, 2019

CI job restarted: jenkins-ci/dynamic-memory-usage

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 15, 2019

components/wifi/esp8266-driver/ESP8266Interface.h

@VeijoPesonen Please rebase and we start CI

@VeijoPesonen
Copy link
Contributor Author

@0xc0170 rebase done.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 15, 2019

CI started

@VeijoPesonen
Copy link
Contributor Author

Something different this time:
The command "W: Failed to fetch http://repo.mongodb.org/apt/ubuntu/dists/trusty/mongodb-org/3.4/Release.gpg The following signatures were invalid: KEYEXPIRED 1515625755" failed 3 times.

@0xc0170
Copy link
Contributor

0xc0170 commented Feb 15, 2019

Travis restarted

@mbed-ci
Copy link

mbed-ci commented Feb 15, 2019

Test run: SUCCESS

Summary: 12 of 12 test jobs passed
Build number : 4
Build artifacts

@cmonr
Copy link
Contributor

cmonr commented Feb 15, 2019

This appears to be sitting on top of some 5.12 changes.
Release label updated.

@cmonr cmonr merged commit 7dbe541 into ARMmbed:master Feb 15, 2019
@VeijoPesonen VeijoPesonen deleted the feature-esp8266_reset_handling branch February 18, 2019 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants