Hi all,
Thanks for all the help.
After much debugging, I found that my NIC for some reason is adding the
802.1Q VLAN tag to all outgoing packets. Since the lwip module doesn't
support VLAN by default it was dropping all incoming packets.
I recompiled the microblaze software but I changed ETHARP_SUPPORT_VLAN to
equal 1 in the lwip opt.h file. Using this new golden image the SNAP board
obtained an IP address and I was able to talk to it with no problems.
Cheers,
Jake Jones.
On Wed, May 23, 2018 at 3:44 PM, Jack Hickish <jackhick...@gmail.com> wrote:
> Hi Jake,
>
> I've seen that the ICAP software initialization fails sometimes on boot.
> However I've never seen a problem with actually using the ICAP module to
> reprogram the device, so this is a back-burner issue for now.
>
> After 240 seconds the microblaze DHCP process times out, and goes with a
> predetermined address. (Not sure if 169.254.3.19 is what is expected, you'd
> have to look through the microblaze code). If you have an fpg file you can
> send over I can try and test it on a SNAP here, for sanity. One other thing
> you might want to try out of desperation is (if your network is noisy)
> running on an isolated network where there is not a lot of superfluous
> broadcast traffic -- the microblaze can only buffer one packet at a time,
> and isn't terribly fast at dealing with them.
>
> Cheers
> Jack
>
> On Wed, 23 May 2018 at 09:09 Adam Isaacson <aisaac...@ska.ac.za> wrote:
>
>> Hi Jake,
>>
>> Maybe this helps. ICAP = Internal Access Configuration Port of the FPGA
>> and it allows the FPGA to reconfigure itself, internally e.g. in the case
>> of the SKARAB, the microblaze can issue a command to reconfigure the FPGA
>> if necessary without having to reset the FPGA externally - very useful
>> functionality indeed.
>>
>> The ICAP should not fail, so maybe there is an issue accessing the
>> internal configuration port? Have you tried a different SNAP board and
>> compared the results? It could be a hardware issue, so this would at least
>> eliminate that issue.
>>
>> My 2c worth.
>>
>>
>>
>>
>>
>>
>> Kind regards,
>>
>> Adam Isaacson
>> South African Radio Astronomy Observatory (SARAO)
>> Hardware Manager
>> Cell: (+27) 825639602 <+27%2082%20563%209602>
>> Tel: (+27) 215067300 <+27%2021%20506%207300>
>> email: aisaac...@ska.ac.za
>>
>>
>> On Wed, May 23, 2018 at 8:35 AM, Jake Jones <jakeljone...@gmail.com>
>> wrote:
>>
>>> Hi Jack,
>>>
>>> Is it normal for the debug messages to say 'ICAP init FAIL'?
>>>
>>> Unfortunately syslog is not very helpful either, here's a summary:
>>> May 23 10:48:32 Antenna-PC dnsmasq-dhcp[29048]: DHCPDISCOVER(eth3)
>>> 00:40:89:41:13:02
>>> May 23 10:48:32 Antenna-PC dnsmasq-dhcp[29048]: DHCPOFFER(eth3)
>>> 169.254.39.125 00:40:89:41:13:02
>>> May 23 10:48:45 Antenna-PC dnsmasq-dhcp[29048]: DHCPDISCOVER(eth3)
>>> 00:40:89:41:13:02
>>> May 23 10:48:45 Antenna-PC dnsmasq-dhcp[29048]: DHCPOFFER(eth3)
>>> 169.254.39.125 00:40:89:41:13:02
>>> ...
>>>
>>> After some testing I can't see anything wrong with the NIC I'm using,
>>> same for the DHCP server. I also compiled a modified golden image that used
>>> SFP port 1 instead of port 0, but ran into the same problems.
>>>
>>> I also noticed that the following debug message appears consistently 240
>>> seconds after programming:
>>> IP A9FE0313 NM FFFF0000 GW 00000000
>>> TAPCP server ready
>>> but there is no network traffic or logs suggesting that this IP was
>>> obtained by the DHCP server. Nonetheless, I tried connecting to it using
>>> this IP but had no success there either.
>>> fpga = casperfpga.CasperFpga('169.254.3.19', port=69)
>>>
>>>
>>> Thanks,
>>> Jake Jones.
>>>
>>> On Tue, May 22, 2018 at 6:07 PM, Jack Hickish <jackhick...@gmail.com>
>>> wrote:
>>>
>>>> Well.... that's not wildly instructive!
>>>> Is there anything telling from the dhcp server, perhaps in syslog?
>>>>
>>>> Cheers
>>>> Jack
>>>>
>>>> On Tue, 22 May 2018 at 11:00 Jake Jones <jakeljone...@gmail.com> wrote:
>>>>
>>>>> Hi Jack,
>>>>>
>>>>> This is the output I get immediately after programming the golden
>>>>> image:
>>>>>
>>>>> ICAP init FAIL
>>>>> # JAM starting
>>>>> using ethernet core gbe_port0
>>>>> MAC 0x004089411302
>>>>> IP 00000000 NM 00000000 GW 00000000
>>>>> link is UP
>>>>> FPGA at 33.6 C [ms 10000]
>>>>> FPGA at 33.6 C [ms 20000]
>>>>> ...
>>>>>
>>>>>
>>>>> Cheers,
>>>>> Jake Jones.
>>>>>
>>>>> On Tue, May 22, 2018 at 3:48 PM, Jack Hickish <jackhick...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi Jake,
>>>>>>
>>>>>> That's interesting, I don't think I've seen this failure mode before.
>>>>>> If you plug a mini usb connector into the SNAP, you can read debug
>>>>>> messages
>>>>>> over this port, using it as an 8N1 115200 baud serial interface. If you
>>>>>> have a xilinx programmer, you could also burn the flash manually with
>>>>>> vivado and the .bin file in the repository, but I don't see why that
>>>>>> should
>>>>>> make any difference.
>>>>>>
>>>>>> Cheers
>>>>>> Jack
>>>>>>
>>>>>> On Tue, 22 May 2018 at 04:24 Jake Jones <jakeljone...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I have an issue trying to program the SNAP board via the 10GbE port.
>>>>>>> When I program the board with a golden image the 10GbE port does not
>>>>>>> obtain
>>>>>>> an ip address.
>>>>>>>
>>>>>>> Investigating further, I:
>>>>>>> 1) Programed the golden image (using snap160t_golden_2018-02-17_1540.fpg
>>>>>>> found in the casper-astro/mlib_devel repository) via the raspberry pi.
>>>>>>> 2) Monitoring the traffic on the 10GbE port using wireshark it can
>>>>>>> be seen that the SNAP board sends DHCP Discover packets which is
>>>>>>> followed
>>>>>>> by a DHCP offer from the server. However the SNAP board never responds
>>>>>>> with
>>>>>>> a DHCP Request. Additionally it doesn't respond to any arp requests.
>>>>>>>
>>>>>>> Is there something I'm missing here? Any help is much appreciated!
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Jake Jones.
>>>>>>>
>>>>>>> --
>>>>>>> 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.
>>>>
>>>
>>> --
>>> 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.
