7
31
Fork
You've already forked blackmagic
23

extending nRF91 support #1778

Open
opened 2024年03月06日 12:57:57 +01:00 by maxd-nordic · 1 comment
maxd-nordic commented 2024年03月06日 12:57:57 +01:00 (Migrated from github.com)
Copy link

Hi!
I've been looking at nRF91 support in BMP. It's nice that we have basic support already, but two things are missing:

  • APPROTECT recovery
  • modem firmware update

I could try to help implementing this. This recovery mechanism seems to relatively straightforward to integrate into BMP, but what about the modem firmware? We deliver it as a zip file and there is a long-ish sequence to get the job done (see here). How would you approach this?

Hi! I've been looking at nRF91 support in BMP. It's nice that we have basic support already, but two things are missing: * APPROTECT recovery * modem firmware update I could try to help implementing this. This recovery mechanism seems to relatively straightforward to integrate into BMP, but what about the modem firmware? We deliver it as a zip file and there is a long-ish sequence to get the job done (see [here](https://github.com/pyocd/pyOCD/blob/5ab5c327987c4c3ba5a37928cac25263d4db7586/pyocd/target/family/target_nRF91.py#L629)). How would you approach this?

👋🏼 Agreed about the "APPROTECT" mechanism being fairly straight forward. With the modem firmware upgrade, BMD being firmware accessed over USB (ignoring, for a moment, BMDA which is another story) we would suggest that the "setup device" logic can be integrated into the nRF91 support directly, but that the actual loading of the firwmare would need to be done either via a tool like bmputil/bmpflash or by wrapping the blob up for GDB and using GDB's load mechanism.

This is particularly of note as we have neither the Flash space, nor the capacity as a USB device to go ingesting a Zip file w/ just 20kiB of SRAM to work in, so any preparation needed of that component must be done by the user or at least on the user's machine.

👋🏼 Agreed about the "APPROTECT" mechanism being fairly straight forward. With the modem firmware upgrade, BMD being firmware accessed over USB (ignoring, for a moment, BMDA which is another story) we would suggest that the "setup device" logic can be integrated into the nRF91 support directly, but that the actual loading of the firwmare would need to be done either via a tool like bmputil/bmpflash or by wrapping the blob up for GDB and using GDB's `load` mechanism. This is particularly of note as we have neither the Flash space, nor the capacity as a USB device to go ingesting a Zip file w/ just 20kiB of SRAM to work in, so any preparation needed of that component must be done by the user or at least on the user's machine.
Sign in to join this conversation.
No Branch/Tag specified
main
fix/pre-bmp-v3-cross-file-cleanup
feature/bmda-remote-comms
ALTracer/feature/aarch64-ident
feature/better-meson-optimisation-handling
feature/am335x-support
feature/esp32-c3-support
feature/cortex-ar-software-breakpoints
feature/unit-testing
feature/windows-usb-serial-interface-naming
fix/bmp-external-spi
ALTracer/feature/bluepillplus-platform
ALTracer/feature/at32f43x-unrdp
feature/const-correctness
ALTracer/feature/fault_handlers
ALTracer/feature/hazard3-ice40-support
fix/ci-cleanup
ALTracer/fix/gdb-10-12-thread
ALTracer/feature/blackpill-f4-adc
ALTracer/fix/cortex-desc-allocfail-report
ALTracer/feature/spi-perf
ALTracer/feature/calibrate_swd
ALTracer/feature/blank-check
feature/avr
v2.0
v1.9
v1.10
v1.8
v2.1.0-rc1
v2.0.0
v2.0.0-rc2
v2.0.0-rc1
v1.9.3
v1.10.2
v1.10.1
v1.10.0
v1.10.0-rc1
v1.10.0-rc0
v1.9.2
v1.8.3
v1.9.1
v1.9.0
v1.9.0-rc1
v1.9.0-rc0
v1.8.2
v1.8.1
v1.8.0
v1.7.1
v1.7
v1.6.2-rc1
1.6.2-rc0
v1.6.1
v1.6
v1.6-rc1
v1.6-rc0
production_01
production_00
Labels
Clear labels
BMD App
Black Magic Debug App (aka. PC hosted) (not firmware)
BMP Firmware
Black Magic Probe Firmware (not PC hosted software)
Bug
Confirmed bug
Build system
Build system
Can't reproduce
Maintainers can't reproduce this problem
CI
Continuous Integration System
Contribution wanted
User contributions welcome
Documentation
Project documentation
Draft
Work in progress draft
Duplicate
This issue or pull request already exists
Enhancement
General project improvement
Feedback wanted
Requires additional submitter feedback
Foreign Host Board
Non Native hardware to runing Black Magic firmware on
GDB
Issue/PR related to GDB
Good first issue
Good for newcommers
HwIssue Mitigation
Solving or mitigating a Hardware issue in Software
Information Needed
Maintainers need more information
NativeHardware
Official Black Magic Debug Hardware
New Host Board
New hardware to run Black Magic firmware on
New Target
New debug target
Off Topic
Something that does not involve the project in any way
Potential Bug
A potential, unconfirmed or very special circumstance bug
Regression
Bug caused by a regression
User Interest Needed
More user interest required before consideration
User Testing Needed
Looking for user testing reports
Won't fix
Outside of the project scope or works as intended
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
blackmagic-debug/blackmagic#1778
Reference in a new issue
blackmagic-debug/blackmagic
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?