Skip to content
This repository has been archived by the owner on Mar 29, 2022. It is now read-only.

How to incerse image size transfer limit #177

Open
Vikesh0355 opened this issue Mar 14, 2019 · 2 comments
Open

How to incerse image size transfer limit #177

Vikesh0355 opened this issue Mar 14, 2019 · 2 comments

Comments

@Vikesh0355
Copy link

I am trying to upload the file size which is in gigabyte but when I am doing "dp.update cycle" it is failed with error that upper limits is 5000000 bytes. So I have following queries, could you clarify?

  1. Is there way to upload actual application software to image repository and update primary and secondary?
  2. Is it possible to update primary itself?
  3. is it possible to install application in actual ROM of pc through secondary?

Bug Report

Problem Summary

Expected Behavior

Actual Behavior

Request for New Functionality

Description of the Desired Feature / Behavior

Example Use

@awwad
Copy link
Contributor

awwad commented Mar 15, 2019

Can you post a copy of the stack trace in the error you're receiving, please?

  1. The readme and demonstration code provide a model showing how you could set up a repository (adding image files, writing metadata, and hosting the image files). See the Delivering an Update portion of the demonstration instructions.
    That includes the addition of image files to the repository. As you can see, the demo calls demo_image_repo.add_target_to_image_repo is called, and you can see that that is copying the image file into a hosted directory, and adding the image file to the repository's metadata in memory. The demonstration then instructs you to call demo_image_repo.write_to_live to write and sign new metadata to disk. Please note that this is demonstration code.
  2. In the current version of the reference implementation, the code in primary.py and demo_primary.py provides the code to handle acquisition, verification, and distribution of metadata and images, and the code in secondary.py and demo_secondary.py provides the code to handle verification for individual ECUs. Your Primary should run both in order to both serve as a distribution hub and update itself. In a later version of the reference implementation, I'll reorganize the code so that Primaries don't need to use the code in secondary.py, since this is inconvenient.
  3. I'm not sure I understand this question. Please clarify?

Please note that the purpose of the demonstration code (in demo/), is to provide a model of how to write your own code that uses the reference implementation to do whatever you need to do.

@Vikesh0355
Copy link
Author

Thank for your support!
Could you clarify question number 2 and 3 that I have written on top of this loop?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants