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

U-Boot mode again #16

Open
5 tasks done
EstebanFuentealba opened this issue May 28, 2023 · 2 comments
Open
5 tasks done

U-Boot mode again #16

EstebanFuentealba opened this issue May 28, 2023 · 2 comments

Comments

@EstebanFuentealba
Copy link
Contributor

Contribution guidelines

I've found a bug and checked that ...

  • ... the problem doesn't occur with the mkdocs or readthedocs themes
  • ... the problem persists when all overrides are removed, i.e. custom_dir, extra_javascript and extra_css
  • ... the documentation does not mention anything about my problem
  • ... there are no open or closed issues that are related to my problem

Description

I was able to flash the DongshanPI-PicoW_DefaultImage system and I also built my own SDK compilation using https://github.com/EstebanFuentealba/DongshanPI-PicoW-Docker. However, now I am unable to enter recording mode because the system automatically boots Linux.

How can I re-access the U-Boot options to flash my SDK again?

Expected behaviour

Access the U-Boot options

Actual behaviour

system automatically boots Linux

Steps to reproduce

  1. I connect DongshanPI PicoW via TTL and USB.
  2. I bridge M4-GND and press the button.
  3. DongshanPI PicoW boots Linux instead of entering SigmaStar (U-Boot).

Package versions

  • Python: python --version
  • MkDocs: mkdocs --version
  • Material: pip show mkdocs-material | grep -E ^Version

Configuration

Help Please!

System information

  • Operating system: Window 10
  • USBToTTL
@EstebanFuentealba
Copy link
Contributor Author

EstebanFuentealba commented May 28, 2023

I found the following commands to enter U-Boot, but I'm also unable to connect it to USBDownloadTool.

/etc/fw_setenv ota_upgrade_status 1
reboot

usb device not recognized window message

@DongshanPI
Copy link
Owner

Hi, I probably understand that the problem you encountered is that you cannot enter the burning mode under uboot. Is there any more detailed operation steps? I need to see your complete operation to judge the problem. You can directly contact us in our communication community Describe your problem in detail in the form of pictures + text, and I will find the reason for you to solve it. https://forums.100ask.net/c/10-category/picow/

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

No branches or pull requests

2 participants