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

Update Linux Starter Guide with 3rd party tool #43

Closed
username223 opened this issue Dec 20, 2020 · 1 comment · Fixed by #47
Closed

Update Linux Starter Guide with 3rd party tool #43

username223 opened this issue Dec 20, 2020 · 1 comment · Fixed by #47

Comments

@username223
Copy link
Contributor

The Linux Start Guide currently instructs the user to run the BLFlashEnv tool which doesn't exist.
The documentation also states that the IO8 pin should be tied to LOW, while the Pine64 BL602 EVB ver 1.1 board requires IO8 to be tied to HIGH in order to flash.

I intend to replace the current guide with docs on how to build and flash the sdk_app_helloworld example.

Should the guide prefer any specific third party tool? Currently I only got blflash to work since bl602tool requires the creation of the entire image manually, without any documentation for this process.

@gamelaster
Copy link
Member

blflash is good. And BLFlashEnv exists, I added the lnik

username223 added a commit to username223/bl602-docs that referenced this issue Dec 29, 2020
Fixes pine64#43.

Old unused images have been removed since they either show the wrong
board or unneeded terminal output.
Existing images have been renamed to make more sense.

`blflash` is used since it was the first tool I could get to work
correctly, and none of the tools I tried had any documentation on making
them work.

Only the `Pine64 BL602 EVB ver 1.1` board is shown since I do not own
any other boards.

Alternative flashing tools added as suggested by user `9names` on Discord.

I am unsure if the `BLDevCube` settings are completely correct, but they
worked for me.

`Pine64-BL602-EVB-ver-11.png` is probably not a very good image since I
know even less about photography/image editing than I do embedded
programming.
username223 added a commit to username223/bl602-docs that referenced this issue Dec 29, 2020
Fixes pine64#43.

Old unused images have been removed since they either show the wrong
board or unneeded terminal output.
Existing images have been renamed to make more sense.

`blflash` is used since it was the first tool I could get to work
correctly, and none of the tools I tried had any documentation on making
them work.

Only the `Pine64 BL602 EVB ver 1.1` board is shown since I do not own
any other boards.

Alternative flashing tools added as suggested by user `9names` on Discord.

I am unsure if the `BLDevCube` settings are completely correct, but they
worked for me.

`Pine64-BL602-EVB-ver-11.png` is probably not a very good image since I
know even less about photography/image editing than I do embedded
programming.

The reference name in `bl602doc_tool/content/Burning_process.rst` is
based on the one in `Examples/helloworld/helloworld.rst`.
username223 added a commit to username223/bl602-docs that referenced this issue Dec 29, 2020
Fixes pine64#43.

Old unused images have been removed since they either show the wrong
board or unneeded terminal output.
Existing images have been renamed to make more sense.

`blflash` is used since it was the first tool I could get to work
correctly, and none of the tools I tried had any documentation on making
them work.

Only the `Pine64 BL602 EVB ver 1.1` board is shown since I do not own
any other boards.

Alternative flashing tools added as suggested by user `9names` on Discord.

I am unsure if the `BLDevCube` settings are completely correct, but they
worked for me.

`Pine64-BL602-EVB-ver-11.png` is probably not a very good image since I
know even less about photography/image editing than I do embedded
programming.

The reference name in `bl602doc_tool/content/Burning_process.rst` is
based on the one in `Examples/helloworld/helloworld.rst`.
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 a pull request may close this issue.

2 participants