ALEXA NXP GIT access is blocked

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

ALEXA NXP GIT access is blocked

Jump to solution
1,353 Views
jorge2
Contributor I

Hi community,

We developed and manufactured custom i.MX8 board with Alexa running. We can't get it to work because there is an NXP git source that is blocked. 

This means we can't run the NXP solution that is supposed to run the NXP Alexa "out-of-the-box" solution.

Porting it from the pre-built image won't work as we also have a custom sound card.

We need the tar AWE_CL_8M.tar.bz2 to test out our i.MX8 board. How can we get access, or can you send it to us?

Thanks!

Jorge Reis

git.jpg

0 Kudos
Reply
1 Solution
1,214 Views
diegoadrian
NXP Employee
NXP Employee

Hello,

Have you tried rebuilding the entire Alexa image but with this repo?

$ repo init -u https://source.codeaurora.org/external/imxsupport/meta-avs-demos -b master -m imx-alexa-sdk-4.9.51-8mq_ga.xml

 Apparently, the git that you are using is an old one.

Furthermore, the AWE_CL_8M.tar.bz2 is the package for the voice hat, that in your case, you are not using it. You will need to select "no" at the time you are running the Alexa SDK script and modify the following file. 

  • cp -v /etc/asound.conf /etc/asound.conf.BACKUP
  • cp -v /etc/asound.conf.Regular /etc/asound.conf

Otherwise, you will use the drivers from hardware that you do not have.

Hope this information could help you.

Best regards,

Diego.

View solution in original post

2 Replies
1,215 Views
diegoadrian
NXP Employee
NXP Employee

Hello,

Have you tried rebuilding the entire Alexa image but with this repo?

$ repo init -u https://source.codeaurora.org/external/imxsupport/meta-avs-demos -b master -m imx-alexa-sdk-4.9.51-8mq_ga.xml

 Apparently, the git that you are using is an old one.

Furthermore, the AWE_CL_8M.tar.bz2 is the package for the voice hat, that in your case, you are not using it. You will need to select "no" at the time you are running the Alexa SDK script and modify the following file. 

  • cp -v /etc/asound.conf /etc/asound.conf.BACKUP
  • cp -v /etc/asound.conf.Regular /etc/asound.conf

Otherwise, you will use the drivers from hardware that you do not have.

Hope this information could help you.

Best regards,

Diego.

1,214 Views
jorge2
Contributor I

Thanks Diego. 

Yes, we are building with that repo.

Your hints about asound.conf were helpful. Our issue is sorted out.

Thanks!

JR

0 Kudos
Reply