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

mfg command error #439

Open
vikrant-proxy opened this issue Jul 10, 2021 · 0 comments
Open

mfg command error #439

vikrant-proxy opened this issue Jul 10, 2021 · 0 comments

Comments

@vikrant-proxy
Copy link
Contributor

I'm trying to use the mfg command with the following newt, and it's running into errors -

$ newt version
Apache Newt 1.10.0-dev / fd9df1e-dirty / 2021-05-17_16:21

I pulled a simple test app with the following details -

targets/nrf52_boot
  app=@mcuboot/boot/mynewt
  bsp=@apache-mynewt-core/hw/bsp/nordic_pca10040
  build_profile=optimized
targets/nrf52_blinky
  app=apps/blinky
  bsp=@apache-mynewt-core/hw/bsp/nordic_pca10040
  build_profile=debug
First complete build step for both targets
$ newt mfg create blinky 1
Error: failed to read manifest file: open <path-to-repo>/bin/targets/nrf52_boot/app/boot/mynewt/manifest.json: no such file or directory

My mfg.yml looks like this -

   mfg.targets:
       -
           name: 'targets/nrf52_boot'
           area: FLASH_AREA_BOOTLOADER
           offset: 0

       -
           name: 'targets/nrf52_blinky'
           area: FLASH_AREA_IMAGE_0
           offset: 0

   mfg.meta:
       area: FLASH_AREA_IMAGE_SCRATCH
       offset: 0

I believe this is because the bootloader binaries have now moved into @mcuboot folder, and newt cannot find them anymore.

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