name-allow: tflite-micro not working anymore?

Hi, I'm setting up my environment on a new laptop. The project I'm working on requires tflite-micro and before I found that I needed to add tflite-micro to the 'name-allow' list in nrf/west.yml.

It doesn't seem to be working anymore? Did this change again?

No. I don't want to use Edge Impulse.

Parents
  • Hi Helgi,

    I tried a few different things and see that adding tflite-micro to an automatic installation of NCS can be done just like you said.

    Meanwhile, I have a "workspace" style project with its own NCS installation, created using our VS Code Extension. On that, I still can't add tflite-micro.
    I tried making syntactically incorrect changes to ncs/west.yml, but west update runs just fine, indicating that it does not depend on the file.
    I don't know why right now though.

    Could you please describe how you are setting up your environment, since it seems that affects how things go.

    Hieu

Reply
  • Hi Helgi,

    I tried a few different things and see that adding tflite-micro to an automatic installation of NCS can be done just like you said.

    Meanwhile, I have a "workspace" style project with its own NCS installation, created using our VS Code Extension. On that, I still can't add tflite-micro.
    I tried making syntactically incorrect changes to ncs/west.yml, but west update runs just fine, indicating that it does not depend on the file.
    I don't know why right now though.

    Could you please describe how you are setting up your environment, since it seems that affects how things go.

    Hieu

Children
  • Hi Hieu,

    there's not really much to say since I'm just starting a blank project. But I am starting a "workspace" with the VSCode extension the as stated before I try to edit ncs/west.yml to get TensorFlow working but it does not work.

    Currently working with copying my old working workspace, but It's not exactly ideal.

  • Hi Helgi,

    It does seem that the workspace project is having a problem now.

    Reading the Zephyr guide regarding West Manifest, I am actually a little confused how it worked for you in the past, since it seems to me that West will always proceed with the west.yml on GitHub in this case, and doesn't actually care about the local file.

    What is the content of the following files on your working workspace? Are they different from the same files in the not-working workspace?

    <workspace>/<app>/west.yml
    <workspace>/.west/config

  • Hi Hieu,

    I think I figured it out! Partially at least. The problem was in the file <workspace>/.west/config
    In my old work space it was :

    [manifest]
    path = nrf
    file = west.yml
    
    [zephyr]
    base = zephyr

    But in the new one it was:

    [manifest]
    path = workspace_name
    file = west.yml
    
    [zephyr]
    base = zephyr

    Changing the file to look like the old one now makes `west update` pull the tflite repo.

    But now I'm back at familiar problem like CONFIG_TENSORFLOW_LITE_MICRO being reassigned to 'n'.

    Additionally I do not see the file <workspace>/<app>/west.yml.

    I won't have time to look into this more today - but I'll update you if I figure it out.

    Thanks for all the help!

Related