Re: [Sound-open-firmware] Real hardware (boards) on which the SOF runs
On 1/31/23 04:26, Gerion Entrup wrote:
Hi Pierre,
Am Montag, 30. Januar 2023, 15:55:47 CET schrieb Pierre-Louis Bossart:
Hi Gerion,
Zephyr support is still very new, if you want to start using it now it has to be clear that you'll have to follow the bleeding edge firmware development on TigerLake+ devices. All previous platforms will not have Zephyr support and have been parked on a long-term XTOS-based support branch.
That is good to know.
The only Intel-based devices you can use for you own development are the Up Extreme i11 boards or TigerLake+ Chromebooks in developer mode. These two sets of devices use the community key and have the DSP configured.
The Extreme i11 boards look promising. Regarding the Chrombooks: I'm not familiar with these devices. Is it possible to use them as a "server"? So reboot and connect to them over SSH while the developer mode stays active?
yes, the 'developer mode' is something that you can set once and it can remain on over reboot cycles. It's not that straightforward but it's not the end of the world either.
see here two examples of Chromebooks used for SOF CI with a Ubuntu setup and kernel/firmware updated for tests run over SSH.
https://sof-ci.01.org/linuxpr/PR4163/build2911/devicetest/index.html?model=C...
https://sof-ci.01.org/linuxpr/PR4163/build2911/devicetest/index.html?model=G...
Note that our default test setup relies on a minimal kernel configuration based on 'make defconfig' + scripts to add what we need, see https://github.com/thesofproject/kconfig/blob/master/kconfig-sof-default.sh
This may need to be improved with your own configurations depending on what you want to test.
Hope this helps.
-Pierre
Hi,
On Tue, 31 Jan 2023, Pierre-Louis Bossart wrote:
On 1/31/23 04:26, Gerion Entrup wrote:
The only Intel-based devices you can use for you own development are the Up Extreme i11 boards or TigerLake+ Chromebooks in developer mode. These two sets of devices use the community key and have the DSP configured.
The Extreme i11 boards look promising.
Regarding the Chrombooks: I'm not familiar with these devices. Is it possible to use them as a "server"? So reboot and connect to them over SSH while the developer mode stays active?
yes, the 'developer mode' is something that you can set once and it can remain on over reboot cycles. It's not that straightforward but it's not the end of the world either.
the typical setup is indeed to have a SSH connection set up between development and target machine. The CrOS developer documentation covers this well: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md
Here's one tutorial written from Zephyr perspective how to setup a Tiger Lake Chromebook and get up and running with Zephyr code on the DSP: https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/xtensa/intel_a...
This guide uses Crouton (to enable the full Zephyr test framework on the tested device), but that is not mandatory. Ssh connections are used to run tests on plain CrOS test images as well: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#...
Br, Kai
Hello all,
Here's one tutorial written from Zephyr perspective how to setup a Tiger
Lake Chromebook and get up and running with Zephyr code on the DSP: That is really helpful. Many thanks. I assume for other CPU vendors supporting SOF on Chromebooks the guide is similar.
Would it possible that some AMD guys comment on (sonly) available Chromebooks for SOF development with the Hifi5 on platform Rembrandt?
Kind regards Martin
-----Ursprüngliche Nachricht----- Von: Sound-open-firmware sound-open-firmware-bounces@alsa-project.org Im Auftrag von Kai Vehmanen Gesendet: Mittwoch, 1. Februar 2023 10:45 An: Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com Cc: sound-open-firmware@alsa-project.org; Gerion Entrup entrup@sra.uni-hannover.de Betreff: Re: [Sound-open-firmware] Real hardware (boards) on which the SOF runs
Hi,
On Tue, 31 Jan 2023, Pierre-Louis Bossart wrote:
On 1/31/23 04:26, Gerion Entrup wrote:
The only Intel-based devices you can use for you own development are the Up Extreme i11 boards or TigerLake+ Chromebooks in developer mode. These two sets of devices use the community key and
have the DSP configured.
The Extreme i11 boards look promising.
Regarding the Chrombooks: I'm not familiar with these devices. Is it possible to use them as a "server"? So reboot and connect to them over SSH while the developer mode stays active?
yes, the 'developer mode' is something that you can set once and it can remain on over reboot cycles. It's not that straightforward but it's not the end of the world either.
the typical setup is indeed to have a SSH connection set up between development and target machine. The CrOS developer documentation covers this well: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md
Here's one tutorial written from Zephyr perspective how to setup a Tiger Lake Chromebook and get up and running with Zephyr code on the DSP: https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/xtensa/intel_a dsp_cavs25/doc/index.rst
This guide uses Crouton (to enable the full Zephyr test framework on the tested device), but that is not mandatory. Ssh connections are used to run tests on plain CrOS test images as well: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md# Set-up-SSH-connection-between-chroot-and-DUT
Br, Kai _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
On Wed, Feb 8, 2023 at 11:26 AM martin.roessler@roessler-netz.de wrote:
Hello all,
Here's one tutorial written from Zephyr perspective how to setup a Tiger
Lake Chromebook and get up and running with Zephyr code on the DSP: That is really helpful. Many thanks. I assume for other CPU vendors supporting SOF on Chromebooks the guide is similar.
I should probably pay more attention to this mailing list
Regarding available devices. You can actually use anything after Geminilake through to modern devices (so what Pierre said, plus CML, JSL and GLK).
Also yes you can use AMD and Mediatek chromebooks as well. AMD should be signed with the open key as well as Mediatek.
Would it possible that some AMD guys comment on (sonly) available Chromebooks for SOF development with the Hifi5 on platform Rembrandt?
Kind regards Martin
-----Ursprüngliche Nachricht----- Von: Sound-open-firmware sound-open-firmware-bounces@alsa-project.org Im Auftrag von Kai Vehmanen Gesendet: Mittwoch, 1. Februar 2023 10:45 An: Pierre-Louis Bossart pierre-louis.bossart@linux.intel.com Cc: sound-open-firmware@alsa-project.org; Gerion Entrup entrup@sra.uni-hannover.de Betreff: Re: [Sound-open-firmware] Real hardware (boards) on which the SOF runs
Hi,
On Tue, 31 Jan 2023, Pierre-Louis Bossart wrote:
On 1/31/23 04:26, Gerion Entrup wrote:
The only Intel-based devices you can use for you own development are the Up Extreme i11 boards or TigerLake+ Chromebooks in developer mode. These two sets of devices use the community key and
have the DSP configured.
The Extreme i11 boards look promising.
Regarding the Chrombooks: I'm not familiar with these devices. Is it possible to use them as a "server"? So reboot and connect to them over SSH while the developer mode stays active?
yes, the 'developer mode' is something that you can set once and it can remain on over reboot cycles. It's not that straightforward but it's not the end of the world either.
the typical setup is indeed to have a SSH connection set up between development and target machine. The CrOS developer documentation covers this well: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_mode.md
Here's one tutorial written from Zephyr perspective how to setup a Tiger Lake Chromebook and get up and running with Zephyr code on the DSP:
https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/xtensa/intel_a dsp_cavs25/doc/index.rst https://github.com/zephyrproject-rtos/zephyr/blob/main/boards/xtensa/intel_adsp_cavs25/doc/index.rst
This guide uses Crouton (to enable the full Zephyr test framework on the tested device), but that is not mandatory. Ssh connections are used to run tests on plain CrOS test images as well:
https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md# Set-up-SSH-connection-between-chroot-and-DUT https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#Set-up-SSH-connection-between-chroot-and-DUT
Br, Kai _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
Sound-open-firmware mailing list -- sound-open-firmware@alsa-project.org To unsubscribe send an email to sound-open-firmware-leave@alsa-project.org
participants (4)
-
Curtis Malainey -
Kai Vehmanen -
martin.roessler＠roessler-netz.de -
Pierre-Louis Bossart