Skip to content

bug fix and add jedec id - #11753

Open
somethingjustlike wants to merge 4 commits into
iNavFlight:maintenance-10.xfrom
somethingjustlike:add-flash-id
Open

bug fix and add jedec id#11753
somethingjustlike wants to merge 4 commits into
iNavFlight:maintenance-10.xfrom
somethingjustlike:add-flash-id

Conversation

@somethingjustlike

Copy link
Copy Markdown
Contributor

GT25Q64EZ and 128EZ are nor flash, So i delect them in w25n.c and add jedec id in m25p16

@github-actions

Copy link
Copy Markdown

Branch Targeting Suggestion

You've targeted the master branch with this PR. Please consider if a version branch might be more appropriate:

  • maintenance-9.x - If your change is backward-compatible and won't create compatibility issues between INAV firmware and Configurator 9.x versions. This will allow your PR to be included in the next 9.x release.

  • maintenance-10.x - If your change introduces compatibility requirements between firmware and configurator that would break 9.x compatibility. This is for PRs which will be included in INAV 10.x

If master is the correct target for this change, no action is needed.


This is an automated suggestion to help route contributions to the appropriate branch.

@github-actions

Copy link
Copy Markdown

Test firmware build ready — commit 5652dcf

Download firmware for PR #11753

243 targets built. Find your board's .hex file by name on that page (e.g. MATEKF405SE.hex). Files are individually downloadable — no GitHub login required.

Development build for testing only. Use Full Chip Erase when flashing.

@sensei-hacker sensei-hacker added this to the 10.0 milestone Aug 2, 2026
@sensei-hacker
sensei-hacker changed the base branch from master to maintenance-10.x August 2, 2026 18:18
@sensei-hacker

Copy link
Copy Markdown
Member

Just an FYI for contributors: The tentative schedule for INAV 10 is to have a full release in mid December. That means RC2 needs to be in early to mid November, which places INAV 10.0RC1 at September 1. Please plan to have any new features for INAV 10.0 ready for RC1 no later than September 1. After that, 10.1 will follow about six to seven months later.

@somethingjustlike

Copy link
Copy Markdown
Contributor Author

Thanks for your information
Could you let me know when can this PR be implemented

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 this pull request may close these issues.

2 participants