Project

General

Profile

Actions

Feature #5772

closed

build of "combined" firmware image for initial flashing during production

Added by laforge 15 days ago. Updated 5 days ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
firmware
Target version:
-
Start date:
11/15/2022
Due date:
% Done:

100%

Spec Reference:

Description

In #5768 mschramm implied that it would be good to have "combined" firmware files for production of devices.

Let us know which particular subset you need (like "trace on simtrace" "cardem on owhw", ...), as I don't think it's required to build a combined image for every APP on every BOARD, right?


Related issues

Related to SIMtrace 2 - Bug #5584: several firmware files apparently do not get builtResolvedHoernchen06/20/2022

Actions
Actions #1

Updated by laforge 15 days ago

Actions #2

Updated by mschramm 15 days ago

  • Related to deleted (Feature #5768: retronetworking logo / artwork)
Actions #3

Updated by mschramm 15 days ago

laforge wrote:

In #5768 mschramm implied that it would be good to have "combined" firmware files for production of devices.

It was SYS#5768, not OS#5768

Actions #4

Updated by Hoernchen 14 days ago

What are you two doing? It was OS#5584.

As for "which ones".. why just publish all files, there is no point filtering, if we want to save bandwidth we should just move all files older than 1-2 years into storage... In practice the combined images are useless except for production flashing and should be "published" internally, but that would even be more work and would not improve anything.

Actions #5

Updated by mschramm 14 days ago

  • Related to Bug #5584: several firmware files apparently do not get built added
Actions #6

Updated by laforge 14 days ago

On Tue, Nov 15, 2022 at 04:22:12PM +0000, Hoernchen wrote:

As for "which ones".. why just publish all files, there is no point filtering, if we want to save bandwidth we should just move all files older than 1-2 years into storage...

it's less about bandwidth than providing even more (maybe even nonsensical) options.

In practice the combined images are useless except for production flashing and should be "published"
internally, but that would even be more work and would not improve anything.

we might compromise by putting them into a sub-directory "production-flash-images" or the like.

Actions #7

Updated by mschramm 14 days ago

Hoernchen wrote in #note-4:

What are you two doing? It was OS#5584.

So true... it is #5584.

In practice the combined images are useless except for production flashing and should be "published" internally, but that would even be more work and would not improve anything.

I only need the "cardem for QMOD" combined image (in the test rig), I can live w/o all the other combinations.

According to lynxis , the owhw test fixture also uses a combined image, and also only the cardem variant. Whereas I'm fine with a 'latest' naming, he wishes to see the combined versions also with version number (e.g. "owhw-cardem-combined-0.8.1.40-5f651.bin" in /all subdir (and "owhw-cardem-combined-latest.bin" in both /all and /latest))

So, the request would go for "cardem for qmod" and "cardem for owhw" combined images.

Actions #8

Updated by laforge 14 days ago

On Wed, Nov 16, 2022 at 10:45:24AM +0000, mschramm wrote:

So, the request would go for "cardem for qmod" and "cardem for owhw" combined images.

what about simtrace2 production? combined "trace for simtrace" to flash that all-in-one?

Actions #9

Updated by lynxis 13 days ago

According to lynxis , the owhw test fixture also uses a combined image, and also only the cardem variant. Whereas I'm fine with a 'latest' naming, he wishes to see the combined versions also with version number (e.g. "owhw-cardem-combined-0.8.1.40-5f651.bin" in /all subdir (and "owhw-cardem-combined-latest.bin" in both /all and /latest))

Small correction: The latest should be only in /latest.
  • /all => e.g. "owhw-cardem-combined-0.8.1.40-5f651.bin"
  • /latest => e.g. "owhw-cardem-combined-latest.bin"

TLDR; I would like to wish a remsim combined image. It is one step less to do something in the wrong way.

Actions #10

Updated by mschramm 13 days ago

laforge wrote in #note-8:

On Wed, Nov 16, 2022 at 10:45:24AM +0000, mschramm wrote:

So, the request would go for "cardem for qmod" and "cardem for owhw" combined images.

what about simtrace2 production? combined "trace for simtrace" to flash that all-in-one?

ping roh ?

Actions #11

Updated by laforge 7 days ago

  • Status changed from New to Resolved
  • Assignee changed from mschramm to laforge
  • % Done changed from 0 to 100

see the various *combined.bin images at https://downloads.osmocom.org/binaries/simtrace2/firmware/latest/

I decided to build cardem for BOARD=ngff-cardem,owhw,qmod and trace for BOARD=simtrace

Actions #12

Updated by mschramm 6 days ago

laforge wrote in #note-11:

see the various *combined.bin images at https://downloads.osmocom.org/binaries/simtrace2/firmware/latest/
I decided to build cardem for BOARD=ngff-cardem,owhw,qmod and trace for BOARD=simtrace

Thanks!

Could someone please purge the dfu-dfu files in the /all subdir (>400 files) ?

Actions #13

Updated by laforge 6 days ago

On Wed, Nov 23, 2022 at 05:16:22PM +0000, mschramm wrote:

Could someone please purge the dfu-dfu files in the /all subdir (>400 files) ?

done.

Actions #14

Updated by roh 5 days ago

laforge wrote in #note-8:

On Wed, Nov 16, 2022 at 10:45:24AM +0000, mschramm wrote:

So, the request would go for "cardem for qmod" and "cardem for owhw" combined images.

what about simtrace2 production? combined "trace for simtrace" to flash that all-in-one?

i have always flashed the bl via bossac ( simtrace-dfu-flash.bin ) and then the trace ( simtrace-trace-dfu.bin ) via dfu in production. i cannot remember using a combined image there ever.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)