From alan at kageds.com Mon Jun 3 09:49:34 2019 From: alan at kageds.com (KageDS) Date: Mon, 3 Jun 2019 10:49:34 +0100 Subject: simtrace2 just sits and does nothing : any suggestions? In-Reply-To: <20190531140823.GL22070@nataraja> References: <8d408eaa-2376-1c42-ebff-69de51fb98f0@kageds.com> <20190530215602.GH22070@nataraja> <86009086-a7ac-4f2e-1339-cb4cc91b9923@kageds.com> <20190531140823.GL22070@nataraja> Message-ID: <45ba736c-fe85-28be-59a6-632e2551530e@kageds.com> Hi Harald, Well it looks like my attempt to solder header pins onto the board has ended in a disaster: I'm now seeing this when I connect the USB. Jun? 3 09:23:23 kageds kernel: [1094465.891611] usb 1-1: new low-speed USB device number 71 using xhci_hcd Jun? 3 09:23:23 kageds kernel: [1094466.011674] usb 1-1: device descriptor read/64, error -71 Jun? 3 09:23:23 kageds kernel: [1094466.239641] usb 1-1: device descriptor read/64, error -71 Jun? 3 09:23:23 kageds kernel: [1094466.467689] usb 1-1: new low-speed USB device number 72 using xhci_hcd Jun? 3 09:23:23 kageds kernel: [1094466.587703] usb 1-1: device descriptor read/64, error -71 Jun? 3 09:23:23 kageds kernel: [1094466.815730] usb 1-1: device descriptor read/64, error -71 Jun? 3 09:23:24 kageds kernel: [1094466.923737] usb usb1-port1: attempt power cycle Jun? 3 09:23:24 kageds kernel: [1094467.567751] usb 1-1: new low-speed USB device number 73 using xhci_hcd Jun? 3 09:23:24 kageds kernel: [1094467.568257] usb 1-1: Device not responding to setup address. Jun? 3 09:23:24 kageds kernel: [1094467.776277] usb 1-1: Device not responding to setup address. Jun? 3 09:23:25 kageds kernel: [1094467.983753] usb 1-1: device not accepting address 73, error -71 Jun? 3 09:23:25 kageds kernel: [1094468.103767] usb 1-1: new low-speed USB device number 74 using xhci_hcd Jun? 3 09:23:25 kageds kernel: [1094468.104244] usb 1-1: Device not responding to setup address. Jun? 3 09:23:25 kageds kernel: [1094468.312219] usb 1-1: Device not responding to setup address. Jun? 3 09:23:25 kageds kernel: [1094468.519831] usb 1-1: device not accepting address 74, error -71 Jun? 3 09:23:25 kageds kernel: [1094468.520812] usb usb1-port1: unable to enumerate USB device I also just see garbage on both debug ports. Though I'm not sure which is pin1 on the headers or what baud rate I should be using. I'm guessing I should send the board back for repair? Any thoughts Thanks Alan On 31/05/2019 15:08, Harald Welte wrote: > Hi Alan, > On Fri, May 31, 2019 at 11:02:50AM +0100, KageDS wrote: > >> FYI The pins are missing on X601 and X701. Looks like I need to dig up some >> header pins as well. > yes, this is intentional. The pin headers were impacting some enclosure ingtegration > of a customer, and we decided to not place them by default. After all, they're not > for use in production. > > I guess we could place them for the 1-off evaluation board purchases, thanks for > pointing that out. > From laforge at gnumonks.org Mon Jun 3 13:57:23 2019 From: laforge at gnumonks.org (Harald Welte) Date: Mon, 3 Jun 2019 15:57:23 +0200 Subject: simtrace2 just sits and does nothing : any suggestions? In-Reply-To: <45ba736c-fe85-28be-59a6-632e2551530e@kageds.com> References: <8d408eaa-2376-1c42-ebff-69de51fb98f0@kageds.com> <20190530215602.GH22070@nataraja> <86009086-a7ac-4f2e-1339-cb4cc91b9923@kageds.com> <20190531140823.GL22070@nataraja> <45ba736c-fe85-28be-59a6-632e2551530e@kageds.com> Message-ID: <20190603135723.GD22070@nataraja> Hi Alan, On Mon, Jun 03, 2019 at 10:49:34AM +0100, KageDS wrote: > Well it looks like my attempt to solder header pins onto the board has ended > in a disaster: Sorry to hear that :/ > I also just see garbage on both debug ports. Though I'm not sure which is > pin1 on the headers or what baud rate I should be using. The pin-out should be in the manual, but isn't. Typically one of the pin has a square copper layer and the others are round, then the square one is GND. I don't have a board with me right now so I cannot verify, but we'll investigate. The baud rate depends on the firmware version. Older versions use 115200 while current master uses 921600 bps. We'll make sure to update the manual to include related information. > I'm guessing I should send the board back for repair? That's probably the best idea. Sorry for the troubles. Please return to sysmocom, we'll make sure to repair, test and return it together with cables for the serial console to get back to the analyzing the actual problems you've been experiencing. Thanks, Harald -- - Harald Welte http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) From alan at kageds.com Thu Jun 13 13:52:09 2019 From: alan at kageds.com (KageDS) Date: Thu, 13 Jun 2019 14:52:09 +0100 Subject: simtrace2 just sits and does nothing : any suggestions? In-Reply-To: <20190603135723.GD22070@nataraja> References: <8d408eaa-2376-1c42-ebff-69de51fb98f0@kageds.com> <20190530215602.GH22070@nataraja> <86009086-a7ac-4f2e-1339-cb4cc91b9923@kageds.com> <20190531140823.GL22070@nataraja> <45ba736c-fe85-28be-59a6-632e2551530e@kageds.com> <20190603135723.GD22070@nataraja> Message-ID: Hi Harald, many thanks for the quick turnaround fixing the board. I've managed to catch the problem on the debug port but not sure how much help it is going to be: ============================================================================= SIMtrace2 firmware 0.4.186-6349 (C) 2010-2016 by Harald Welte ============================================================================= -I- Chip ID: 0x28900960 (Ext 0x00000000) -I- Serial Nr. 51203120-39513450-32303031-32333037 -I- Reset Cause: general reset (first power-up reset) -I- Detected Quad-Modem ST12 -I- VERSION_DET ADC=3731 => 3003455 uVund -I- USB init... USBD_Init Std gDesc Dev Std sAddr SetAddr(11) Std gDesc Dev Std gDesc Qua -W- Sta 0x888A8. -I- calling init of config 1... -I- 536881924: CLK activateda work-around -I- Modem 0: physical SIM -I- 0: Use local/physical SIM -I- Modem 1: physical SIM -I- 1: Use local/physical SIM -I- entering main loop... -I- 0: Card Detect Status -1 -> 0 -I- 1: Card Detect Status -1 -> 0 -I- USB is now configured Std sInterface -W- Sta 0x88828 [0] -W- _ Std cFeat Hlt Std cFeat Hlt Std cFeat D -I- Modem 0: virtual SIM -I- 0: Use remote/emulated SIM -I- 0: ATR set: 3b 00 -I- 0: Asserting modem reset -I- 0: De-asserting modem reset -I- 0: ATR set: 3b 9e 96 80 1f c7 80 31 e0 73 fe 21 1b 66 d0 02 17 8d 11 00 89 Regards Alan On 03/06/2019 14:57, Harald Welte wrote: > Hi Alan, > > On Mon, Jun 03, 2019 at 10:49:34AM +0100, KageDS wrote: >> Well it looks like my attempt to solder header pins onto the board has ended >> in a disaster: > Sorry to hear that :/ > >> I also just see garbage on both debug ports. Though I'm not sure which is >> pin1 on the headers or what baud rate I should be using. > The pin-out should be in the manual, but isn't. Typically one of the pin has a > square copper layer and the others are round, then the square one is GND. I don't > have a board with me right now so I cannot verify, but we'll investigate. > > The baud rate depends on the firmware version. Older versions use 115200 while current > master uses 921600 bps. > > We'll make sure to update the manual to include related information. > >> I'm guessing I should send the board back for repair? > That's probably the best idea. Sorry for the troubles. Please return > to sysmocom, we'll make sure to repair, test and return it together with > cables for the serial console to get back to the analyzing the actual > problems you've been experiencing. > > Thanks, > Harald