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

Durandal: manual logger start fails #13483

Closed
mhkabir opened this issue Nov 15, 2019 · 16 comments
Closed

Durandal: manual logger start fails #13483

mhkabir opened this issue Nov 15, 2019 · 16 comments
Assignees
Labels

Comments

@mhkabir
Copy link
Member

mhkabir commented Nov 15, 2019

Starting logger on Durandal (stm32h7_support branch) manually from Mavlink console seems to fail:

image

It does report that a new log file was opened, after logger on:
image

However these files are always empty:

image

@dagar
Copy link
Member

dagar commented Nov 15, 2019

@davids5
Copy link
Member

davids5 commented Nov 15, 2019

@mhkabir - I think there may be a power sequencing issue with the SD.
What does dmesg show?

@LorenzMeier LorenzMeier removed the bug label Nov 15, 2019
@LorenzMeier
Copy link
Member

@mhkabir How do you power the unit? We have flown successfully with valid logs. I presume you did start that on the bench?

@davids5 I have confirmed the power sequencing issue. Steps:

  • Remove the SD card
  • Unpower Durandal
  • Plug USB in
  • Plug the SD card in BEFORE the boot loader lights go out
  • run logger stop && logger start -e

@LorenzMeier
Copy link
Member

I would leave this issue open so we can add an errata to the documentation @hamishwillee as a known hardware limitation if powered via USB. But it is not a software issue per se (and maybe we can work around it in SW later).

@mhkabir
Copy link
Member Author

mhkabir commented Nov 15, 2019

@LorenzMeier yes, this is on bench, powered from USB only.

  • I'm powering via USB only.

  • Logging does work if it's started from boot. (SDLOG_MODE)
    image

  • I didn't touch the SD card.

@mhkabir
Copy link
Member Author

mhkabir commented Nov 15, 2019

@davids5 from dmesg, after running logger start
image

@stale
Copy link

stale bot commented Feb 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. Thank you for your contributions.

@stale stale bot added the stale label Feb 13, 2020
@dagar dagar added the bug label Apr 8, 2020
@stale stale bot removed the stale label Apr 8, 2020
@dagar dagar added this to the Release v1.11.0 milestone Apr 8, 2020
@ShiauweiZhao
Copy link
Contributor

have a plan to solve it?I also encountered the same problem。

@davids5
Copy link
Member

davids5 commented Apr 17, 2020

@zhaoxiaowei1013 This was addressed in #14592

Please test current master and reopen this issues if it did not solve it.

@davids5 davids5 closed this as completed Apr 17, 2020
@jareiko
Copy link

jareiko commented Apr 21, 2020

I'm still sometimes getting what might be this problem on master, running off battery power.

At some point the SD card seems to fail, and then nothing works anymore (logging or sd_bench, for example).

Screenshot from 2020-04-21 16-27-58

@dagar
Copy link
Member

dagar commented Apr 21, 2020

@jareiko could you open a new issue for that and start collecting any relevant data?

Is that console screenshot showing anything other than logger successfully starting?

Have you noticed any patterns? Does it fail after a certain period of time? Are you getting any potentially relevant error messages from logger or the system? You could check dmesg output.

@jareiko
Copy link

jareiko commented Apr 21, 2020

That is just a dmesg log, as requested earlier in the thread. Yes, I'll start a new issue for this when I'm looking at it again. For now we're exploring log streaming instead.

@davids5
Copy link
Member

davids5 commented Apr 21, 2020

@jareiko - Also have you tried another card?

@jareiko
Copy link

jareiko commented Apr 21, 2020

Yes, three different cards, all of which work fine on a Pixhawk 4.

@ShiauweiZhao
Copy link
Contributor

This problem still exists. I tested this problem in the latest master branch
Screenshot from 2020-04-23 10-49-20
And all in my cuav v5+ is work good.

@davids5
Copy link
Member

davids5 commented Jun 29, 2020

Resolved by PX4/NuttX#106

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

No branches or pull requests

6 participants