Great, let’s discuss Model Library Format a bit further on another RFC. I will try to start one early this week.
and a new command
tvmc micro gen-project
(or something) would be added to generate the e.g. Zephyr project.oh that’s cool. Copying (or generating) it from the template dir you mentioned right?
Yes. However, to refine this a bit and address a comment you made earlier to @manupa-arm: this template project shouldn’t get used if we are just producing Model Library Format. The idea of the template project is to provide the necessary boilerplate/glue to configure an SoC to run a model given one in Model Library Format. The template project is tied to the implementation of the Project-level API.
Right, I think it is not indeed necessary to pass the SDK (like
zephyr
) to thecompile
command because I understandbuild.relay
doesn’t need to know anything about the “board” (contrary to what is used in the prototype of this RFC document) and about the SDK used.tvmc micro build
maybe should address it?
I think that sounds ok at a high level.
For this, I’d propose that an e.g. git sha1 of the Project API repo should be enough.
Sorry, I could not follow you here.
Here I mean–if we are going to include something to describe the device configuration (similar to the --target=zephyr -target=stm32f746xx -board=...
you proposed), the portion which describes the project template used should just be the git sha1 from the git repo that houses the template project and the Project-level API implementation.
By “device serial numbers” do you mean the usb serial device number? If so currently we allow only one of such a device to be available and it’s probed, failing if more than 1 serial port is available no? Maybe we should stick with that default and add an option to the user to specify it when desired. Anyway, I think that info should not be in the metadata, it should be left by the user to specify when
tvmc micro flash
andtvmc run
is executed?
Yeah that’s right, but you could override or choose a specific port when multiple identical boards are connected. I agree it should not be in metadata and instead passed to flash
or run
either explicitly on the command-line or in a .gitignore
’d environment config file.