Products > Test Equipment

Agilent MSO-X 3014A not booting past Ref/Math/Digital/Serial LEDs

<< < (3/6) > >>

TheSteve:
Keysight did have a service note indicating that NAND corruption would be covered past the original warranty date. However I believe the extended coverage provided by the service note has expired. I don't think you'll find they will still do a no charge repair. Always worth asking of course.

99.9% of the time NAND corruption can be fixed yourself.

If you're seeing any LED's flash/turn on then there should be serial data output. Double(triple) check your connections and terminal settings, chances are something isn't correct.

james_s:
There's probably a good chance it's the flash, but I'd start with some simple checks. Confirm the power supply voltage(s) are present and within a reasonable tolerance. Check any oscillators you can find and make sure they're putting out something. See if you can find the reset line for the CPU and see what it's doing. Look at the bus and see if there's any activity. Of course a lot of this relies on having access to another oscilloscope.

switchabl:
Most likely there is a problem with your serial connection. If you see flashing LEDs, I think the boot process is getting at least as far as the Windows CE bootloader. So supply voltages and clock (at least for the main processor) are almost certainly fine. And like TheSteve said, there should at least be some activity on the serial console. at that stage

Make sure you don't have the RX and TX pins swapped (try connecting the RX pin of your adapter to either to be sure). Check your serial adapter on something else to make sure you have it set up correctly, maybe the serial console on a Raspberry Pi or some other SBC that you may have lying around. If nothing else helps, check the 3000X TX pin with a second oscillscope to make sure that there is any activity at all.

Also, I've had signal integrity issues with cheap USB<->UART adapters before and adding a USB isolator or using a laptop running on battery may help in that case.

elemenoh:
Well of course I had RX/TX mixed up despite checking several times. Anyway, I'm in now and will continue to follow the steps in the other thread. Thanks for the help so far everyone.


--- Code: ---U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  fsmc-ecc1 128 MiB
In:    serial
Out:   serial
Err:   serial
SerNum:serial number not programmed
Chip:  BD Board Rev: 4
Net:   smsc
Press space to stop autoboot:  0
## Booting kernel from Legacy Image at f8050000 ...
   Image Name:   PBOOT
   Created:      2011-08-24  22:35:34 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36045 Bytes = 35.2 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Aug 24 2011 15:15:48
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008


System ready!
Preparing for download...
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOXOXOOOOXXOOOOOOOOOXOOOOXOXXOXOXXOOOXOXXXXXOOXXXOOOOOOXOOXXXOXXOOOXOXXOOXXOXOOOXOOXOOXXOOOXOOOOXOXOOOOOXOOOXOOXOXXXXXOXOXOXOXXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOXOOOXOOX
OOOOOXXOOOOOXOOXOOXXOOOOOOOOOXOOOOXOOOOOOOXXOOOOOXXOOOOOOOXOOOOXOXOOOOXOOOXOOXOOXOOXOXOXOOXOXOXXOXOOOXXXOOXXOXXOOOXXXXOXOOXOXOOOOXOOOOXOOOXOOERROR: Checksum failure (expected=0x6F6450  computed=0x6F64F4)
****** Checksum failure on record 125, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x13064E8  Name="" Target=RAM
 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000

BL_IMAGE_TYPE_UNKNOWN

 Loading image 2 failed, trying next one
 All images failed

Press r to reset
--- End code ---

TheSteve:
Good Good, standard NAND corruption. Hopefully the fix goes well.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod