Jump to content

rs485 kills red-brick


Guest piwo
 Share

Recommended Posts

hallo !

 

habe rs485-netzwerk mit stepdown von 26v in jeder node :

 

( red + ethernet-ext + rs485-ext) <---> (1-3 master-bricks + rs-485) <---> ....

... <---> (1-3 master-bricks + rs-485)

 

der red ist eine eigene node damit der stromverbrauch des usb-gsm-dongles & der ethernet-extension nicht zu instabilitäten führt

 

PROBLEM(E):

 

1) der brick "stirbt" mit folgenden system-log-einträgen "send verification failed" - SIEHE :

 

2016-01-13 17:27:29.542519 <I> <network.c:373> Added new client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:27:34.211817 <I> <client.c:220> Client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:27:34.211991 <W> <client.c:381> Destroying client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled) while 1 request(s) are still pending

2016-01-13 17:27:35.212141 <W> <zombie.c:96> Destroying zombie (id: 5) while 1 request(s) are still pending

2016-01-13 17:27:36.248623 <I> <network.c:373> Added new client (N: 192.168.1.40:60877, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:27:42.809263 <I> <client.c:220> Client (N: 127.0.0.1:49521, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:27:46.856486 <I> <network.c:373> Added new client (N: 127.0.0.1:49522, T: plain-socket, H: 25, A: disabled)

2016-01-13 17:28:13.881132 <I> <client.c:220> Client (N: 127.0.0.1:49522, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:28:19.897407 <I> <client.c:220> Client (N: 192.168.1.40:60877, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:28:22.118107 <I> <network.c:373> Added new client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled)

2016-01-13 17:28:26.080620 <I> <network.c:373> Added new client (N: 127.0.0.1:49523, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:28:44.106513 <I> <client.c:220> Client (N: 127.0.0.1:49523, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:29:32.533394 <I> <client.c:220> Client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:29:32.533780 <W> <client.c:381> Destroying client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled) while 1 request(s) are still pending

2016-01-13 17:29:33.533987 <W> <zombie.c:96> Destroying zombie (id: 6) while 1 request(s) are still pending

2016-01-13 23:58:05.188141 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-13 23:58:05.202755 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-14 01:48:03.064621 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-14 01:48:03.078639 <E> <red_rs485_extension.c:370> Send verification failed

 

2016-01-13 17:27:29.542519 <I> <network.c:373> Added new client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:27:34.211817 <I> <client.c:220> Client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:27:34.211991 <W> <client.c:381> Destroying client (N: 192.168.1.40:60875, T: plain-socket, H: 26, A: disabled) while 1 request(s) are still pending

2016-01-13 17:27:35.212141 <W> <zombie.c:96> Destroying zombie (id: 5) while 1 request(s) are still pending

2016-01-13 17:27:36.248623 <I> <network.c:373> Added new client (N: 192.168.1.40:60877, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:27:42.809263 <I> <client.c:220> Client (N: 127.0.0.1:49521, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:27:46.856486 <I> <network.c:373> Added new client (N: 127.0.0.1:49522, T: plain-socket, H: 25, A: disabled)

2016-01-13 17:28:13.881132 <I> <client.c:220> Client (N: 127.0.0.1:49522, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:28:19.897407 <I> <client.c:220> Client (N: 192.168.1.40:60877, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:28:22.118107 <I> <network.c:373> Added new client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled)

2016-01-13 17:28:26.080620 <I> <network.c:373> Added new client (N: 127.0.0.1:49523, T: plain-socket, H: 26, A: disabled)

2016-01-13 17:28:44.106513 <I> <client.c:220> Client (N: 127.0.0.1:49523, T: plain-socket, H: 26, A: disabled) disconnected by peer

2016-01-13 17:29:32.533394 <I> <client.c:220> Client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled) disconnected by peer

2016-01-13 17:29:32.533780 <W> <client.c:381> Destroying client (N: 192.168.1.40:60883, T: plain-socket, H: 25, A: disabled) while 1 request(s) are still pending

2016-01-13 17:29:33.533987 <W> <zombie.c:96> Destroying zombie (id: 6) while 1 request(s) are still pending

2016-01-13 23:58:05.188141 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-13 23:58:05.202755 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-14 01:48:03.064621 <E> <red_rs485_extension.c:370> Send verification failed

2016-01-14 01:48:03.078639 <E> <red_rs485_extension.c:370> Send verification failed

 

...

 

ethernet funktioniert auch nicht mehr obwohl die grüne led brav blinkt & wenn ich über den mini-usb an die serielle console will um nachzusehen, so höre die leds auf zu blinken und das wars ...

 

die einzige forschungsmöglichkeit ist nachträglich das log anzusehen ;-((

 

startup sieht in etwa so aus :

 

2016-01-16 20:18:05.473927 <I> <main_linux.c:281> Brick Daemon 2.2.1~hf2+redbrick started (daemonized)

2016-01-16 20:18:07.166600 <I> <red_extension.c:598> Found Ethernet Extension at position 0

2016-01-16 20:18:07.663515 <I> <red_stack.c:531> SPI stack slave discovery done. Found 0 slave(s) with 0 UID(s) in total

2016-01-16 20:18:14.882619 <I> <red_extension.c:584> Found RS485 Extension at position 1

2016-01-16 20:18:14.882813 <I> <red_rs485_extension.c:904> Initializing extension subsystem

2016-01-16 20:18:14.883174 <I> <red_rs485_extension.c:304> Baudrate configured = 50000, Effective baudrate = 50000.000000

2016-01-16 20:18:14.883370 <I> <red_rs485_extension.c:333> Serial interface initialized

2016-01-16 20:18:14.883408 <I> <red_rs485_extension.c:647> Initialized RS485 RXE state

2016-01-16 20:18:14.883497 <I> <red_rs485_extension.c:998> Initialized as master

2016-01-16 20:18:14.896523 <I> <redapid.c:309> Connected to RED Brick API Daemon

2016-01-16 20:18:14.896882 <I> <red_stack.c:552> Starting reinitialization of SPI slaves

...

 

---

 

2) generell (auch wenn der obige fehler noch nicht aufgetreten ist) gibt es ein problem über usb von windows-7 aus über den mini-usb an die serielle console hernazukommen :

 

das gerät wird nicht erkannt & im devicemanager verbleibt ein unerkanntes gerät

 

neuinstallation vom brickviewer/brickdaemon am windows-7 hat (noch) nicht geholfen ...

 

---

 

was kann ich da nun tun ?

 

lg

w

 

 

 

 

Link to comment
Share on other sites

 

 

UPDATE :

 

habe fast einen tag verbracht mit forschen und bin auf die glorreiche idee gekommen, den red-brick (und auch die rs485-extension) zu tauschen ...

 

bei dem ersatz-red-brick funktioniert die serielle schnittstelle sobald die led auf grün blinkend geht --> ersuche um rma auf dem kurzen wege bei meiner nächsten bestellung !!!

 

ob ein offensichtlicher hardwaredefekt am red die ursache des send_verification-problems war werde ich beobachten müssen ...

 

ich werde das hier berichten .....

 

lgw

Link to comment
Share on other sites

danke für den prompten tausch !!!

 

bis jetzt gibt es keine "brösel" am ersatz-red.

hoffe das bleibt so ....

 

aber vielleicht sollte ich den defekten doch zurücksenden und man könnte dann das noch untersuchen -

vielleicht liegen ein paar platinenverbindungen oder smd-bauteile arg nah an den befestigungslöchern - oder kann man sonst was mechanisch vermurksen ...

 

(n.b. ich will keine arbeit machen oder den zurückschicken und er landet dann doch in der rundablage ... aber ich finde das ganze doch sehr sehr seltsam)

lg

w

Link to comment
Share on other sites

hab dmesg beim defekten red (serial console wird nicht mit usb_modeswitch geswitcht) mit dem ersatz-red verglichen :

 

[4 sekunden pause ]

[    8.871946] incomplete xfer (0x20)

 

[    5.272390] insmod_device_driver

 

[    5.272406] [sw_udc]: sw_usb_device_enable start

[    5.272415] [sw_udc]: usb_vbase  = 0xf1c13000

[    5.272424] [sw_udc]: sram_vbase = 0xf1c00000

[    5.272449] [sw_udc]: open_usb_clock

[    5.369673] [sw_udc]: CONFIG_USB_GADGET_DUALSPEED

[    5.369696] [sw_udc]: usbd_start_work

[    5.369704] [sw_udc]: sw_usb_device_enable end

[    5.425154] [sw_udc]: IRQ: suspend

[    5.425181] [sw_udc]: ERR: usb speed is unkown

[    5.432366] usb 2-1: new high-speed USB device number 2 using sw-ehci

[    5.535214] [sw_udc]: IRQ: reset

[    5.535240] [sw_udc]: irq: reset happen, throw away all urb

[    5.583854] [sw_udc]:

[    5.583872] +++++++++++++++++++++++++++++++++++++

[    5.583879] [sw_udc]:  usb enter high speed.

[    5.583887] [sw_udc]:

[    5.583891] +++++++++++++++++++++++++++++++++++++

[    5.584103] [sw_udc]: Set address 4

[    5.604014] RED Brick gadget: high-speed config #1: foobar

[    5.604037] [sw_udc]: ep enable: ep1(0x80805c14, ep1-bulk, 128, 512)

[    5.604058] [sw_udc]: ep enable: ep2(0x80805c60, ep2-bulk, 0, 512)

[    5.604086] [sw_udc]: ep enable: ep5(0x80805d44, ep5-int, 128, 10)

[    5.604101] [sw_udc]: ep enable: ep3(0x80805cac, ep3-bulk, 128, 512)

[    5.604113] [sw_udc]: ep enable: ep4(0x80805cf8, ep4-bulk, 0, 512)

[    5.612877] scsi0 : usb-storage 2-1:1.0

[    6.613766] scsi 0:0:0:0: CD-ROM            HSPA    USB SCSI CD-ROM  2.31 PQ: 0 ANSI: 2

[    6.619439] sr0: scsi-1 drive

[    6.619463] cdrom: Uniform CD-ROM driver Revision: 3.20

[    6.619887] sr 0:0:0:0: Attached scsi CD-ROM sr0

[    7.702606] ehci_irq: port change detect

[    7.702709] usb 2-1: USB disconnect, device number 2

[    7.803043] ehci_irq: port change detect

[    8.102314] usb 2-1: new high-speed USB device number 3 using sw-ehci

[    8.739153] usbcore: registered new interface driver usbserial

[    8.739170] usbserial: USB Serial Driver core

[    8.799570] usbcore: registered new interface driver option

[    8.799885] USB Serial support registered for GSM modem (1-port)

[    8.800193] option 2-1:1.0: GSM modem (1-port) converter detected

[    8.810290] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0

[    8.810506] option 2-1:1.1: GSM modem (1-port) converter detected

[    8.812849] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1

[    8.813099] option 2-1:1.3: GSM modem (1-port) converter detected

[    8.815238] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2

[    9.953234] w5x00: 2.0.0

[    9.953300] w5x00 probe [int 17, rst 15, sel 0, mac 40:d8:55:2:a4:95]

[    9.953310] chip select before: 0

[  10.808661] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85500)

[  10.808688] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85880)

[  10.808701] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85640)

[  10.808712] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85680)

[  10.808724] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed856c0)

[  10.808735] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed854c0)

[  10.808749] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85000)

[  10.808760] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85800)

[  10.808773] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85700)

[  10.808785] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85740)

[  10.808797] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed857c0)

[  10.808809] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85840)

[  10.808821] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85980)

[  10.808832] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85940)

[  10.808844] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed859c0)

[  10.808855] [sw_udc]: alloc request: ep(0x80805cf8, ep4-bulk, 512), req(0x9ed85a00)

[  10.808867] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85a40)

[  10.808879] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85a80)

[  10.808890] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85ac0)

[  10.808902] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85b00)

[  10.808914] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85b40)

[  10.808926] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85b80)

[  10.808937] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85bc0)

[  10.808948] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85c00)

[  10.808960] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85c40)

[  10.808972] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85c80)

[  10.808984] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85cc0)

[  10.808995] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85d00)

[  10.809006] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85d40)

[  10.809018] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85d80)

[  10.809030] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85dc0)

[  10.809042] [sw_udc]: alloc request: ep(0x80805cac, ep3-bulk, 512), req(0x9ed85e00)

 

ohne dass ich jetzt einen kurs in sunxi udc machen muss - wie kann ich da noch weiter prüfen ???

 

lg

w

 

 

 

 

Link to comment
Share on other sites

Mit usb_modeswitch hat das nicht zu tun. Der RED Brick ist ein USB Composite Device mit einem Vendor Specific Interface (Tinkerforge API) und einem CDC-ACM Interface (serielle Schnittstelle).

 

Der RED Brick sollte als zwei Devices im Geräte Manager auftauchen: "RED Brick" und "RED Brick Serial Console".

 

Taucht der problematische RED Brick nur als ein unbekanntes Gerät auf, oder taucht das "RED Brick" Gerät, aber das "RED Brick Serial Console" nicht auf?

 

Ich würde auf ersteres tippen, das würde zu einem Hardwäredefekt passen. Da kannst du softwaremäßig nichts machen und nichts debuggen.

 

Das zweite Log vom RED Brick sieht normal aus

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...