[hpsdr] Hermes Documentation
John Marvin
jm-hpsdr at themarvins.org
Sat Oct 27 03:38:36 PDT 2012
Okay, so it appears that the problem is that DEBUG_LEDx doesn't always
equal LEDx as far as the illustrated picture goes (I assume that the
DEBUG_LED order is a hardware bit order, and they don't correspond to
the order on the board due to a board layout optimization). I would
assume that for sanity purposes from a user perspective who doesn't look
at the source code, that the leds should be numbered according to the
order inferred from the illustrated topside Hermes picture, i.e. such
that LEDx = D(20-x). From my observation D12 is the DHCP status led. If
the LEDs are numbered in reverse order then that should be LED8.
However, that corresponds to DEBUG_LED7 according to the mapping below.
So what Phil says is what is true for the source code, but I would think
that the manual should document things in the order they appear on the
board (i.e. LED #'s not DEBUG_LED#'s). Putting things together I think
the mapping is:
LED1 = D19 = DEBUG_LED1
LED2 = D18 = DEBUG_LED2
LED3 = D17 = DEBUG_LED3
LED4 = D16 = DEBUG_LED4
LED5 = D15 = DEBUG_LED5
LED6 = D14 = DEBUG_LED8
LED7 = D13 = DEBUG_LED6
LED8 = D12 = DEBUG_LED7
LED9 = D11 = DEBUG_LED9
LED10 = D10 = DEBUG_LED10
i.e. for leds 6,7 and 8 LEDx != DEBUG_LEDx
Does that make sense, or am I confused? If I'm not confused, should the
documentation in the manual be changed to correspond to the LED order,
rather than the DEBUG_LED order? Other options would be to 1) change the
illustration and document the LED #'s in an out of order sequence so
that LEDx = DEBUG_LEDx (i.e change LEDx so that LEDx always equals
DEBUG_LEDx), or 2) change the source code and schematics in order to
make the DEBUG_LED #'s be in the sequential order that they appear on
the board (i.e. change DEBUG_LEDx so that DEBUG_LEDx always equals LEDx).
Thanks,
John
On 10/26/2012 11:37 PM, Phil Harman wrote:
> Hi Dick,
>
> Just checked in the Hermes source code and these are the LED
> designations:
>
> DEBUG_LED1 - Lights when an Ethernet broadcast is detected
> DEBUG_LED2 - Lights when traffic to the boards MAC address is
> detected
> DEBUG_LED3 - Lights when detect a received sequence error or ASMI
> is busy
> DEBUG_LED4 - Displays state of PHY negotiations - fast flash
> if no Ethernet connection, slow flash if 100T and on if 1000T
> DEBUG_LED5 - Lights when the PHY receives Ethernet traffic
> DEBUG_LED6 - Lights when the PHY transmits Ethernet traffic
> DEBUG_LED7 - Displays state of DHCP negotiations or static IP -
> on if ACK, slow flash if NAK, fast flash if time out
> and long then short flash if static IP
> DEBUG_LED8 - Lights when sync (0x7F7F7F) received from PC
> DEBUG_LED9 - Lights when a Metis discovery packet is received
> DEBUG_LED10 - Lights when a Metis discovery packet reply is sent
>
>
> 73 Phil....VK6APH
>
>
>
> -----Original Message----- From: Dick Faust
> Sent: Friday, October 26, 2012 6:14 AM
> To: John Marvin ; Phil Harman ; HPSDR
> Subject: Re: [hpsdr] Hermes Documentation
>
> John,
> Thank you for the info.
> Corrections to Page 11 & 12 are done.
>
> Page 13 - D6 is on front panel Status Led and corrected.
>
> The other LED's have an issue and appear to be labeled out of sequence.
> I have not had my board up and running yet so I need some help here.
>
> Manual v1.7
> LED1: Lights when an Ethernet broadcast is detected.
> LED2: Lights when traffic to the board’s MAC address is detected.
> LED3: Lights when detecting a received sequence error or the ASMI is
> busy.
> LED4: Displays state of PHY negotiations – there is a fast flash if no
> Ethernet connection;a slow flash if 100T; and a steady ‘on’ if 1000T.
> LED5: Lights when the PHY receives Ethernet traffic.
> LED6: Lights when the PHY transmits Ethernet traffic.
> LED7: Displays state of DHCP negotiations or static IP – the LED is on
> if ACK;displays a slow flash if NAK; fast flash if time out; and long
> flash then short flash if static IP.
> LED8: Lights when sync (0x7F7F7F) is received from the personal computer.
> LED9: Lights when a Hermes discovery packet is received.
> LED10: Lights when a Hermes discovery packet reply is sent.
>
> Schematic
> LED1 = D19 -> Debug_LED1
> LED2 = D18 -> Debug_LED2
> LED3 = D17 -> Debug_LED3
> LED4 = D16 -> Debug_LED4
> LED5 = D15 -> Debug_LED5
> LED6 = *D13* -> Debug_LED6
> LED7 = *D12* -> Debug_LED7
> LED8 = *D14* -> Debug_LED8
> LED9 =* D11* -> Debug_LED9
> LED10 = D10 -> Debug_LED10
>
> Can some one please verify that this is correct.
>
> 73, Dick
>
> John Marvin wrote:
>> ***** High Performance Software Defined Radio Discussion List *****
>>
>> Here are some documentation problems and/or posssible enhancements I
>> found:
>>
>> 1) Page 11: Documentation for J11 says that it provides an open drain
>> PTT output that is common with pin 13 on J16. However the
>> documentation for J16 says that pin 13 is user digital input 4, and
>> that pin 25 is the PTT output.
>>
>> 2) Page 12: Document says that J27 (Left speaker output) is not
>> fitted during manufacture. It's present on my Hermes board.
>>
>> 3) Page 13 documents the various LED's. Later on there is text that
>> says this is subject to change, so I don't know if the intention is
>> to keep this part of the document up to date with the latest firmware
>> or not. I noticed one error and one possible enhancement:
>>
>> a) LED8 appears to be the DHCP status led, not LED7.
>> b) There's reference to a "STATUS LED" that flashes twice per second.
>> This appears to be D6 currently. Should D6 be documented as the
>> status led?
>>
>> Regards,
>>
>> John
>> AC0ZG
>>
>> On 10/22/2012 10:38 PM, Dick Faust wrote:
>>> ***** High Performance Software Defined Radio Discussion List *****
>>>
>>> I am working with Phil to update the Hermes manual version 1.7
>>>
>>> To assist with list questions, I am posting on my website the current
>>> and temporary information.
>>>
>>> There is a preliminary change notice [not finished]
>>> A photo of the TAPR build top side that needs component identification
>>> And an updated bottom side view [hopeful finished] that should clear up
>>> the power supply questions.
>>>
>>> Direct Links below:
>>>
>>> <!-- /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal
>>> {mso-style-parent:""; margin:0in; margin-bottom:.0001pt;
>>> mso-pagination:widow-orphan; font-size:12.0pt; font-family:Arial;
>>> mso-fareast-font-family:"Times New Roman"; mso-bidi-font-family:"Times
>>> New Roman";} a:link, span.MsoHyperlink {color:blue;
>>> text-decoration:underline; text-underline:single;} a:visited,
>>> span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;
>>> text-underline:single;} @page Section1 {size:8.5in 11.0in; margin:1.0in
>>> 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in;
>>> mso-paper-source:0;} div.Section1 {page:Section1;} -->
>>>
>>> http://k9ivb.net\Hermes\Prelim_CN_4_Hermes_UM_v1.7.doc
>>> <http://k9ivb.net/Hermes/Prelim_CN_4_Hermes_UM_v1.7.doc>
>>>
>>> http://k9ivb.net\Hermes\Tapr_Hermes_top.JPG
>>> <http://k9ivb.net/Hermes/Tapr_Hermes_top.JPG>
>>>
>>> http://k9ivb.net\Hermes\TAPR_Hermes_back_ilst.jpg
>>> <http://k9ivb.net/Hermes/TAPR_Hermes_back_ilst.jpg>
>>>
>>>
>>> If anyone finds any errors please let me know.
>>>
>>> the word version of the v1.7 manual can be found at:
>>> http://svn.tapr.org/repos_sdr_hpsdr/trunk/Hermes/Documentation/
>>>
>>> 73, Dick Faust K9IVB
>>> _______________________________________________
>>> HPSDR Discussion List
>>> To post msg: hpsdr at openhpsdr.org
>>> Subscription help:
>>> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>>> HPSDR web page: http://openhpsdr.org
>>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>
>> _______________________________________________
>> HPSDR Discussion List
>> To post msg: hpsdr at openhpsdr.org
>> Subscription help:
>> http://lists.openhpsdr.org/listinfo.cgi/hpsdr-openhpsdr.org
>> HPSDR web page: http://openhpsdr.org
>> Archives: http://lists.openhpsdr.org/pipermail/hpsdr-openhpsdr.org/
>>
>
1351334316.0
More information about the Hpsdr
mailing list