Re: [casper] Booting SKARAB

[Adam Isaacson]

Hi Amit,

I am assuming you are compiling a CASPER toolflow image and that you are
able to program the CASPER toolflow image on the SKARAB via the 1GbE? If
so, then your MTU sizes are fine and then it should work for the 40GbE as
well

You should have the following versions for the SKA-SA BSP as shown below
when you read back via python using casperfpga - please confirm:

In [9]: fpga2.transport.get_skarab_version_info()
Out[9]: {'emdedded_software_version': '3.4.0',
 'golden_image': False,
 'microblaze_hardware_version': '2.5',
 'multiboot_image': True,
 'spartan_firmware_version': '1.6',
 'toolflow_image': False,
 'virtex7_firmware_version': '2.5'}

If any of the above is different then let me know.

What version of casperfpga are you using? You should be using the latest
from devel branch https://github.com/ska-sa/casperfpga/tree/devel. I am
using this version:

In [2]: casperfpga.__version__  (this is the command to read back the
casperfpga version)
Out[2]: '0.4.4.dev508+devel.16fce79'

Please confirm if this is different then try update to the latest.

Kind regards,

Adam




On Mon, Jan 8, 2018 at 3:12 PM, Amit Bansod 
wrote:

> Hi Adam,
>
> Thanks for the updates.
>
> I have one issue with casperfpga tools. After I changed the golden and
> boot images as well as Spartan fpga firmware (from
> https://github.com/ska-sa/skarab_bsp_images) to support CASPER toolflow (
> https://github.com/ska-sa/mlib_devel), I am able to compile and program
> the SKARAB using casperfpga with 1GbE port but connection via 40GbE needs
> reprogramming of the fpga. It also often complains about the MTU to be set
> to 9000 even though it is already set on our switch as well as linux
> machine.  Does the 40G core MTU needs to be manually set as well ?
>
> Kind regards,
> Amit
>
>
> On 08-Jan-18 1:41 PM, Adam Isaacson wrote:
>
> Hi Amit,
>
> Yes, I can confirm that no porting has been done regarding the SKARAB ADC
> here at SKA-SA. We are planning on holding a yellow block creation workshop
> here at SKA some time later this year - date TBC.  The user can bring their
> hardware with firmware and get it running during the workshop.
>
> I can confirm that the rest of the SKARAB is fully supported using the
> CASPER tools. The only other limitation, is that the CASPER tools are
> supporting only one 40GbE TX/RX link on the SKARAB. If you desire more than
> one link then it should not require much effort to update. We are chasing
> deadlines at the moment, so it is not possible for us to address the above
> at this time.
>
> Kind regards,
>
> Adam
>
>
>
> On Mon, Jan 8, 2018 at 12:16 PM, Clifford van Dyk <
> cliffordvan...@gmail.com> wrote:
>
>> Hello Amit
>>
>> Thanks, and Happy New Year to you too!
>>
>> I am fairly certain that no one has started porting the SKARAB ADC
>> firmware into a CASPER "yellow block" just yet. I would be happy to support
>> you on this. I don't see any limitations due to the new ADC interface.
>>
>> The Peralex-supplied JESD receiver core (included in the BSP) may need to
>> be adapted depending on your application (how the ADC is configured) - the
>> Peralex core is not currently a "generic" JESD core, rather it is designed
>> to receive JESD packets from the specific ADC configured with specific
>> mode/options (most notably output bandwidth). It may be easiest to start
>> porting this to yellow block directly first, and then parameterise/extend
>> the firmware/yellow block to support other ADC modes (decimation rates, DDC
>> bypass, etc) as needed.
>>
>> There are a few restrictions that you need to be aware of in terms of
>> bandwidth/resolution trade-off if you change the ADC modes, particularly
>> when bypassing the ADC's built-in DDCs. If you can give me an idea of how
>> you specifically intend to use the ADC (mode/bandwidth/frequency band), I
>> can perhaps offer you some further advice.
>>
>> Kind regards,
>> Clifford
>>
>>
>>
>> On 1/8/2018 10:30 AM, Amit Bansod wrote:
>>
>> Hi Clifford,
>>
>> Happy New Year!
>>
>> Thanks a lot for the BSP Package. I am going through the documentation
>> now and have one SKARAB with casper firmware and one with Peralex.
>>
>> I would be interested to develop a Casper "yellow block" for SKARAB since
>> most of our development is using CASPER toolflow. Do you know if anybody is
>> already working on it or if there are any limitations due to the new ADC
>> interface ?
>>
>> Regards,
>> Amit
>>
>>
>> On 20-Dec-17 7:15 PM, Clifford van Dyk wrote:
>>
>> Hi Amit
>>
>> Your Skarab would have been shipped with a firmware that supports DHCP on
>> all GbE interfaces and bootloading over 1GbE (only). It includes support
>> for the ADC mezzanine. You will probably need to use the Peralex BSP tools
>> to access and boot the Skarab over 1GbE, rather than the CASPER toolflow.
>>
>> If you would like to work with the CASPER tools, then you will need to
>> overwrite the Peralex boot image with the CASPER boot image. This will
>> provide additional support for booting the Skara

Re: [casper] Booting SKARAB

[Amit Bansod]

Hi Adam,

Thanks for the updates.

I have one issue with casperfpga tools. After I changed the golden and
boot images as well as Spartan fpga firmware (from
https://github.com/ska-sa/skarab_bsp_images) to support CASPER toolflow
(https://github.com/ska-sa/mlib_devel), I am able to compile and program
the SKARAB using casperfpga with 1GbE port but connection via 40GbE
needs reprogramming of the fpga. It also often complains about the MTU
to be set to 9000 even though it is already set on our switch as well as
linux machine.  Does the 40G core MTU needs to be manually set as well ?

Kind regards,
Amit

On 08-Jan-18 1:41 PM, Adam Isaacson wrote:
> Hi Amit,
>
> Yes, I can confirm that no porting has been done regarding the SKARAB
> ADC here at SKA-SA. We are planning on holding a yellow block creation
> workshop here at SKA some time later this year - date TBC.  The user
> can bring their hardware with firmware and get it running during the
> workshop. 
>
> I can confirm that the rest of the SKARAB is fully supported using the
> CASPER tools. The only other limitation, is that the CASPER tools are
> supporting only one 40GbE TX/RX link on the SKARAB. If you desire more
> than one link then it should not require much effort to update. We are
> chasing deadlines at the moment, so it is not possible for us to
> address the above at this time.
>
> Kind regards,
>
> Adam
>
>   
>
> On Mon, Jan 8, 2018 at 12:16 PM, Clifford van Dyk
> mailto:cliffordvan...@gmail.com>> wrote:
>
> Hello Amit
>
> Thanks, and Happy New Year to you too!
>
> I am fairly certain that no one has started porting the SKARAB ADC
> firmware into a CASPER "yellow block" just yet. I would be happy
> to support you on this. I don't see any limitations due to the new
> ADC interface.
>
> The Peralex-supplied JESD receiver core (included in the BSP) may
> need to be adapted depending on your application (how the ADC is
> configured) - the Peralex core is not currently a "generic" JESD
> core, rather it is designed to receive JESD packets from the
> specific ADC configured with specific mode/options (most notably
> output bandwidth). It may be easiest to start porting this to
> yellow block directly first, and then parameterise/extend the
> firmware/yellow block to support other ADC modes (decimation
> rates, DDC bypass, etc) as needed.
>
> There are a few restrictions that you need to be aware of in terms
> of bandwidth/resolution trade-off if you change the ADC modes,
> particularly when bypassing the ADC's built-in DDCs. If you can
> give me an idea of how you specifically intend to use the ADC
> (mode/bandwidth/frequency band), I can perhaps offer you some
> further advice.
>
> Kind regards,
> Clifford
>
>
>
> On 1/8/2018 10:30 AM, Amit Bansod wrote:
>> Hi Clifford,
>>
>> Happy New Year!
>>
>> Thanks a lot for the BSP Package. I am going through the
>> documentation now and have one SKARAB with casper firmware and
>> one with Peralex.
>>
>> I would be interested to develop a Casper "yellow block" for
>> SKARAB since most of our development is using CASPER toolflow. Do
>> you know if anybody is already working on it or if there are any
>> limitations due to the new ADC interface ?
>>
>> Regards,
>> Amit
>>
>>
>> On 20-Dec-17 7:15 PM, Clifford van Dyk wrote:
>>>
>>> Hi Amit
>>>
>>> Your Skarab would have been shipped with a firmware that
>>> supports DHCP on all GbE interfaces and bootloading over 1GbE
>>> (only). It includes support for the ADC mezzanine. You will
>>> probably need to use the Peralex BSP tools to access and boot
>>> the Skarab over 1GbE, rather than the CASPER toolflow.
>>>
>>> If you would like to work with the CASPER tools, then you will
>>> need to overwrite the Peralex boot image with the CASPER boot
>>> image. This will provide additional support for booting the
>>> Skarab over 40GbE, but you will loose support for the ADC. The
>>> ADC firmware is currently provided as HDL code only-it has yet
>>> to be ported into a CASPER yellow block.
>>>
>>> I will pop by the office tomorrow to provide you with a link
>>> where you can download the Peralex BSP.
>>>
>>> Kind regards,
>>> Clifford
>>>
>>>
>>> On 20 Dec 2017 6:05 PM, "Amit Bansod" >> > wrote:
>>>
>>> Dear All,
>>>
>>> I am trying to boot SKARAB and the it gets stuck at "ARP
>>> ENTRY ID:0
>>> IP:". Is there any way to force a static ip address or
>>> boot via 1GbE
>>> interface as well ?
>>>
>>> Many Thanks!
>>>
>>> Regards,
>>> Amit
>>>
>>> --
>>> You received this message because you are subscribed to the
>>> Google Groups "casper@lists.berkeley.edu
>>> " group.
>>> To unsubscribe 

Re: [casper] Booting SKARAB

[Adam Isaacson]

Hi Amit,

Yes, I can confirm that no porting has been done regarding the SKARAB ADC
here at SKA-SA. We are planning on holding a yellow block creation workshop
here at SKA some time later this year - date TBC.  The user can bring their
hardware with firmware and get it running during the workshop.

I can confirm that the rest of the SKARAB is fully supported using the
CASPER tools. The only other limitation, is that the CASPER tools are
supporting only one 40GbE TX/RX link on the SKARAB. If you desire more than
one link then it should not require much effort to update. We are chasing
deadlines at the moment, so it is not possible for us to address the above
at this time.

Kind regards,

Adam



On Mon, Jan 8, 2018 at 12:16 PM, Clifford van Dyk 
wrote:

> Hello Amit
>
> Thanks, and Happy New Year to you too!
>
> I am fairly certain that no one has started porting the SKARAB ADC
> firmware into a CASPER "yellow block" just yet. I would be happy to support
> you on this. I don't see any limitations due to the new ADC interface.
>
> The Peralex-supplied JESD receiver core (included in the BSP) may need to
> be adapted depending on your application (how the ADC is configured) - the
> Peralex core is not currently a "generic" JESD core, rather it is designed
> to receive JESD packets from the specific ADC configured with specific
> mode/options (most notably output bandwidth). It may be easiest to start
> porting this to yellow block directly first, and then parameterise/extend
> the firmware/yellow block to support other ADC modes (decimation rates, DDC
> bypass, etc) as needed.
>
> There are a few restrictions that you need to be aware of in terms of
> bandwidth/resolution trade-off if you change the ADC modes, particularly
> when bypassing the ADC's built-in DDCs. If you can give me an idea of how
> you specifically intend to use the ADC (mode/bandwidth/frequency band), I
> can perhaps offer you some further advice.
>
> Kind regards,
> Clifford
>
>
>
> On 1/8/2018 10:30 AM, Amit Bansod wrote:
>
> Hi Clifford,
>
> Happy New Year!
>
> Thanks a lot for the BSP Package. I am going through the documentation now
> and have one SKARAB with casper firmware and one with Peralex.
>
> I would be interested to develop a Casper "yellow block" for SKARAB since
> most of our development is using CASPER toolflow. Do you know if anybody is
> already working on it or if there are any limitations due to the new ADC
> interface ?
>
> Regards,
> Amit
>
>
> On 20-Dec-17 7:15 PM, Clifford van Dyk wrote:
>
> Hi Amit
>
> Your Skarab would have been shipped with a firmware that supports DHCP on
> all GbE interfaces and bootloading over 1GbE (only). It includes support
> for the ADC mezzanine. You will probably need to use the Peralex BSP tools
> to access and boot the Skarab over 1GbE, rather than the CASPER toolflow.
>
> If you would like to work with the CASPER tools, then you will need to
> overwrite the Peralex boot image with the CASPER boot image. This will
> provide additional support for booting the Skarab over 40GbE, but you will
> loose support for the ADC. The ADC firmware is currently provided as HDL
> code only-it has yet to be ported into a CASPER yellow block.
>
> I will pop by the office tomorrow to provide you with a link where you can
> download the Peralex BSP.
>
> Kind regards,
> Clifford
>
> On 20 Dec 2017 6:05 PM, "Amit Bansod"  wrote:
>
>> Dear All,
>>
>> I am trying to boot SKARAB and the it gets stuck at "ARP ENTRY ID:0
>> IP:". Is there any way to force a static ip address or boot via 1GbE
>> interface as well ?
>>
>> Many Thanks!
>>
>> Regards,
>> Amit
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to casper+unsubscr...@lists.berkeley.edu.
>> To post to this group, send email to casper@lists.berkeley.edu.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "casper@lists.berkeley.edu"  group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "casper@lists.berkeley.edu"  group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.
>
>
> --
> You received this message because you are subscribed to the Google Groups "
> casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to casper+unsubscr...@lists.berkeley.edu.
> To post to this group, send email to casper@lists.berkeley.edu.
>



-- 
[image: SKA_banner]

Best Regards / Vriendelike Groete

*Adam Isaacson*
Hardware Manager

[image: SKA_bann

Re: [casper] Booting SKARAB

[Clifford van Dyk]

Hello Amit

Thanks, and Happy New Year to you too!

I am fairly certain that no one has started porting the SKARAB ADC
firmware into a CASPER "yellow block" just yet. I would be happy to
support you on this. I don't see any limitations due to the new ADC
interface.

The Peralex-supplied JESD receiver core (included in the BSP) may need
to be adapted depending on your application (how the ADC is configured)
- the Peralex core is not currently a "generic" JESD core, rather it is
designed to receive JESD packets from the specific ADC configured with
specific mode/options (most notably output bandwidth). It may be easiest
to start porting this to yellow block directly first, and then
parameterise/extend the firmware/yellow block to support other ADC modes
(decimation rates, DDC bypass, etc) as needed.

There are a few restrictions that you need to be aware of in terms of
bandwidth/resolution trade-off if you change the ADC modes, particularly
when bypassing the ADC's built-in DDCs. If you can give me an idea of
how you specifically intend to use the ADC (mode/bandwidth/frequency
band), I can perhaps offer you some further advice.

Kind regards,
Clifford


On 1/8/2018 10:30 AM, Amit Bansod wrote:
> Hi Clifford,
>
> Happy New Year!
>
> Thanks a lot for the BSP Package. I am going through the documentation
> now and have one SKARAB with casper firmware and one with Peralex.
>
> I would be interested to develop a Casper "yellow block" for SKARAB
> since most of our development is using CASPER toolflow. Do you know if
> anybody is already working on it or if there are any limitations due
> to the new ADC interface ?
>
> Regards,
> Amit
>
>
> On 20-Dec-17 7:15 PM, Clifford van Dyk wrote:
>>
>> Hi Amit
>>
>> Your Skarab would have been shipped with a firmware that supports
>> DHCP on all GbE interfaces and bootloading over 1GbE (only). It
>> includes support for the ADC mezzanine. You will probably need to use
>> the Peralex BSP tools to access and boot the Skarab over 1GbE, rather
>> than the CASPER toolflow.
>>
>> If you would like to work with the CASPER tools, then you will need
>> to overwrite the Peralex boot image with the CASPER boot image. This
>> will provide additional support for booting the Skarab over 40GbE,
>> but you will loose support for the ADC. The ADC firmware is currently
>> provided as HDL code only-it has yet to be ported into a CASPER
>> yellow block.
>>
>> I will pop by the office tomorrow to provide you with a link where
>> you can download the Peralex BSP.
>>
>> Kind regards,
>> Clifford
>>
>>
>> On 20 Dec 2017 6:05 PM, "Amit Bansod" > > wrote:
>>
>> Dear All,
>>
>> I am trying to boot SKARAB and the it gets stuck at "ARP ENTRY ID:0
>> IP:". Is there any way to force a static ip address or boot
>> via 1GbE
>> interface as well ?
>>
>> Many Thanks!
>>
>> Regards,
>> Amit
>>
>> --
>> You received this message because you are subscribed to the
>> Google Groups "casper@lists.berkeley.edu
>> " group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to casper+unsubscr...@lists.berkeley.edu
>> .
>> To post to this group, send email to casper@lists.berkeley.edu
>> .
>>
>> -- 
>> You received this message because you are subscribed to the Google
>> Groups "casper@lists.berkeley.edu" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to casper+unsubscr...@lists.berkeley.edu
>> .
>> To post to this group, send email to casper@lists.berkeley.edu
>> .
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to casper+unsubscr...@lists.berkeley.edu
> .
> To post to this group, send email to casper@lists.berkeley.edu
> .


-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.

Re: [casper] Booting SKARAB

[Amit Bansod]

Hi Clifford,

Happy New Year!

Thanks a lot for the BSP Package. I am going through the documentation
now and have one SKARAB with casper firmware and one with Peralex.

I would be interested to develop a Casper "yellow block" for SKARAB
since most of our development is using CASPER toolflow. Do you know if
anybody is already working on it or if there are any limitations due to
the new ADC interface ?

Regards,
Amit


On 20-Dec-17 7:15 PM, Clifford van Dyk wrote:
>
> Hi Amit
>
> Your Skarab would have been shipped with a firmware that supports DHCP
> on all GbE interfaces and bootloading over 1GbE (only). It includes
> support for the ADC mezzanine. You will probably need to use the
> Peralex BSP tools to access and boot the Skarab over 1GbE, rather than
> the CASPER toolflow.
>
> If you would like to work with the CASPER tools, then you will need to
> overwrite the Peralex boot image with the CASPER boot image. This will
> provide additional support for booting the Skarab over 40GbE, but you
> will loose support for the ADC. The ADC firmware is currently provided
> as HDL code only-it has yet to be ported into a CASPER yellow block.
>
> I will pop by the office tomorrow to provide you with a link where you
> can download the Peralex BSP.
>
> Kind regards,
> Clifford
>
>
> On 20 Dec 2017 6:05 PM, "Amit Bansod"  > wrote:
>
> Dear All,
>
> I am trying to boot SKARAB and the it gets stuck at "ARP ENTRY ID:0
> IP:". Is there any way to force a static ip address or boot
> via 1GbE
> interface as well ?
>
> Many Thanks!
>
> Regards,
> Amit
>
> --
> You received this message because you are subscribed to the Google
> Groups "casper@lists.berkeley.edu
> " group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to casper+unsubscr...@lists.berkeley.edu
> .
> To post to this group, send email to casper@lists.berkeley.edu
> .
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "casper@lists.berkeley.edu" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to casper+unsubscr...@lists.berkeley.edu
> .
> To post to this group, send email to casper@lists.berkeley.edu
> .

-- 
You received this message because you are subscribed to the Google Groups 
"casper@lists.berkeley.edu" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to casper+unsubscr...@lists.berkeley.edu.
To post to this group, send email to casper@lists.berkeley.edu.