ERROR: Bad Username or Password
Home › Forums › Conduit: AEP Model › ERROR: Bad Username or Password
Tagged: # conduit factory reset
- This topic has 11 replies, 3 voices, and was last updated 4 years, 11 months ago by
Darrik Spaude.
-
AuthorPosts
-
June 5, 2020 at 11:41 am #30672
Claudia De luna
ParticipantHi,
I have a Conduit MTCDT (MTCDP-210A_US-EU-GB running 1.4.1 to which I do not have the login credentials. I have tried to reset it using the front panel reset button to no avail. I can ping the default IP and hit the GUI login page but always get ERROR: Bad Username or Password (admin/admin and I also tried some root options in a fit of desperation). Same with SSH, I can get a log in prompt but can’t login. Have I missed something in the re-set procedure (held down more than 20 seconds)? Are there any other options anyone can suggest. One of my goals it so upgrade it to at least 1.4.3 but can’t get past the login.
Any guidance would be very much appreciated!!
Thank you!
Claudia
June 5, 2020 at 12:58 pm #30674Jeff Hatch
KeymasterClaudia,
Try holding in the reset button for more than 30s. That should factor default the device unless the boot has not fully completed. There is a possibility that a boot script is failing before the process that monitors for the factory reset.
Jeff
June 5, 2020 at 1:00 pm #30675Claudia De luna
ParticipantHi Jeff,
I’ve done that several times for like 45 seconds and a minute. I’ll try it again and report back. I’ve not re-set it for an hour so let me do that now.
Thanks!
June 5, 2020 at 1:55 pm #30676Claudia De luna
ParticipantOK..Ive not done anything to the unit for an hour.
I’ve removed the LoRa module (I had removed the antenna and it was not coming up at all).
One the green PWR light is on. No other lights.Its not pingable and Link is down on the Ethernet interface.
Held the reset button for 60 seconds.
PWR light stayed on for a few seconds and is now off. After about 15 seconds the first three lights lit, a few seconds moe and the LS light went out. Then all lights went off, now power light back on.
At about 2m30s PWR light on only. Still not pinging.
At 9 minutes ping response. PWR and STATUS lit.
At 10 minutes all power LEDs off and ping response stopped. PWR sort of blinking.
10:49 PWR STATUS LS green
11:22 ping response
11:50 PWR STATUS green LS no longer lit.At about 12min PWR solid STATUS now blinking. Still pinging but still can’t log in. Eventually it stops responding to pings.
June 5, 2020 at 3:02 pm #30677Jeff Hatch
KeymasterHello Claudia,
Can you hook up a debug cable to the port behind the “Multitech” cover on the front of the device? The output of that port will tell how far the boot is getting, ie. ROMBOOT, u-boot, Linux. I believe the cable required is a USB Micro-B.
Jeff
June 5, 2020 at 3:18 pm #30678Claudia De luna
ParticipantSorry! I should have thought to do that to include in the initial request!
This been at:
Switching slow clock to external oscillator…
for a few minutes._ _____ ____ / \ | ____| | _ \ / _ \ | _| | |_) | / ___ \ _ | |___ _ | __/_ /_/ \_\(_)|_____|(_)|_| (_) MultiTech Systems Application Execution Platform with mLinux GNU/Linux mLinux 3.3.5 mtcdt /dev/ttyS0 Version: 1.4.1 Date: 2017-04-07T16:31:49 mtcdt login: RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 NAND: Done to load image U-Boot 2012.10-mtcdt-r6 (Apr 07 2017 - 16:20:16) CPU: AT91SAM9G25 Crystal frequency: 12 MHz CPU clock : 400 MHz Master clock : 133.333 MHz I2C: ready DRAM: 256 MiB WARNING: Caches not enabled NAND: 256 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial vendor-id: Multi-Tech Systems product-id: MTCDT-210A device-id: 19146912 hw-version: MTCDT-0.0 mac-addr: 00:08:00:4a:1d:66 Net: macb0 Hit any key to stop autoboot: 0 Loading from nand0, offset 0x200000 Image Name: mLinux/3.12.27/mtcdt Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3081325 Bytes = 2.9 MiB Load Address: 20008000 Entry Point: 20008000 Bit flip in data area, byte_pos: 960, bit_pos: 0, 0x55 -> 0x54 RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 NAND: Done to load image U-Boot 2012.10-mtcdt-r6 (Apr 07 2017 - 16:20:16) CPU: AT91SAM9G25 Crystal frequency: 12 MHz CPU clock : 400 MHz Master clock : 133.333 MHz I2C: ready DRAM: 256 MiB WARNING: Caches not enabled NAND: 256 MiB RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 NAND: Done to load image U-Boot 2012.10-mtcdt-r6 (Apr 07 2017 - 16:20:16) CPU: AT91SAM9G25 Crystal frequency: 12 MHz CPU clock : 400 MHz Master clock : 133.333 MHz I2C: ready DRAM: 256 MiB WARNING: Caches not enabled NAND: 256 MiB RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 NAND: Done to load image Switching slow clock to external oscillator...
June 5, 2020 at 3:32 pm #30679Jeff Hatch
KeymasterClaudia,
It looks like it is getting to u-boot and then failing to load the kernel. Not sure exactly what happened.
You should be able to drop into u-boot. The most straight forward way to do that is to “power the device” by pulling power, and after reconnecting power, in the terminal hit any key fast enough so that it drops directly into u-boot and doesn’t try to load the kernel. At that point run a print command and let me know what the u-boot environment is.
From there it would be a matter of setting up a TFTP server and I can get you some scripts to run in u-boot to set up the u-boot env to do TFTP. From there you will be able to flash the kernel.
Jeff
-
This reply was modified 4 years, 11 months ago by
Jeff Hatch.
June 5, 2020 at 3:51 pm #30681Claudia De luna
ParticipantIt looks like it goes into U-boot and then keeps booting? Not sure if I got what you needed.
Let me know if now and Ill give it another go
did you see that CRC error??
U-Boot 2012.10-mtcdt-r6 (Apr 07 2017 - 16:20:16) CPU: AT91SAM9G25 Crystal frequency: 12 MHz CPU clock : 400 MHz Master clock : 133.333 MHz I2C: ready DRAM: 256 MiB WARNING: Caches not enabled NAND: 256 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial vendor-id: Multi-Tech Systems product-id: MTCDT-210A device-id: 19146912 hw-version: MTCDT-0.0 mac-addr: 00:08:00:4a:1d:66 Net: macb0 Hit any key to stop autoboot: 0 U-Boot> print baudrate=115200 bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2 bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr} bootdelay=0 ethact=macb0 ethaddr=00:08:00:4a:1d:66 hostname=AT91SAM9G25 ipaddr=192.168.2.1 kernel_addr=0x200000 loadaddr=0x22000000 netmask=255.255.255.0 serverip=192.168.2.2 stderr=serial stdin=serial stdout=serial Environment size: 410/131067 bytes U-Boot> RomBOOT AT91Bootstrap 3.5.3-r2 (Fri Apr 7 16:20:16 CDT 2017) NAND: ONFI flash detected NAND: Manufacturer ID: 0x2c Chip ID: 0x32 NAND: Disable On-Die ECC NAND: Initialize PMECC params, cap: 0x4, sector: 0x200 NAND: Image: Copy 0x80000 bytes from 0x40000 to 0x2ef00000 NAND: Done to load image U-Boot 2012.10-mtcdt-r6 (Apr 07 2017 - 16:20:16) CPU: AT91SAM9G25 Crystal frequency: 12 MHz CPU clock : 400 MHz Master clock : 133.333 MHz I2C: ready DRAM: 256 MiB WARNING: Caches not enabled NAND: 256 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial vendor-id: Multi-Tech Systems product-id: MTCDT-210A device-id: 19146912 hw-version: MTCDT-0.0 mac-addr: 00:08:00:4a:1d:66 Net: macb0 Hit any key to stop autoboot: 0 Loading from nand0, offset 0x200000 Image Name: mLinux/3.12.27/mtcdt Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3081325 Bytes = 2.9 MiB Load Address: 20008000 Entry Point: 20008000 Bit flip in data area, byte_pos: 960
June 5, 2020 at 4:09 pm #30682Darrik Spaude
KeymasterAre you able to stop the reboot? There is a point right away in U-boot where if you press a key it will stop the boot and stay at the U-boot> prompt.
June 5, 2020 at 4:11 pm #30683Claudia De luna
ParticipantSort of…
It sopped enough for me to enter print…but then it keeps going.
Are these the boot parameters you were looking for?:U-Boot> print baudrate=115200 bootargs=mem=256M console=ttyS0,115200 root=/dev/mtdblock8 ro rootfstype=jffs2 bootcmd=nboot.jffs2 ${loadaddr} 0 ${kernel_addr}; bootm ${loadaddr} bootdelay=0 ethact=macb0 ethaddr=00:08:00:4a:1d:66 hostname=AT91SAM9G25 ipaddr=192.168.2.1 kernel_addr=0x200000 loadaddr=0x22000000 netmask=255.255.255.0 serverip=192.168.2.2 stderr=serial stdin=serial stdout=serial Environment size: 410/131067 bytes U-Boot> RomBOOT
June 5, 2020 at 4:42 pm #30684Claudia De luna
ParticipantI can’t thank you enough for all the help. I know its getting late in the day on Friday for you. If there is any documentation you can send me to maybe upgrade or flash a new image and get u-boot set up for tftp that would be really great. My boss is expecting a report on the Conduit on Monday to determine its suitability for our application so I’ve got the weekend to get a good demo set up for him. – Thank you again!
June 5, 2020 at 5:07 pm #30685Darrik Spaude
KeymasterI see that you have a support case already, so let’s keep working through that case.
-
This reply was modified 4 years, 11 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.