Jump to content


Photo

How to enable serial console on boot?


  • Please log in to reply
14 replies to this topic

#1 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 01 September 2011 - 07:33 PM

Well the topic asks it all? I have soldered in a serial hookup to my Dropad A8X, but I cant get a boot log from the bugger. Is there something I need to do in order for it to enable the boot serial console? What are the proper serial port settings?

I am confident my hardware setup is working and proper. I am quite familiar with this sort of stuff, which is why I am so confused. This is usually pretty straight forward.

All tips, tricks, info, and advice are warmly welcome.

#2 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 13 September 2011 - 07:36 AM

Here is an update. Turns out I just had the wrong serial terminal settings. I must say there is NO room inside the dropad for a TRS connector, so for now I just did this: Posted Image

I am using my Universal USB Serial Debug Cables I make and offer for a fair price to willing developers:
Posted Image


With some minor mods you can get a small 2.5mm TRS jack up at the top where the GPS antenna is. Once I get one I will fit it in, take some pics, and maybe to a writeup. If you dont plan on doing any Dropad kernel work, this is not needed.
Posted Image

An example of how universal this kit is, and the thing is, its been done this way since the 1970's. I didnt come up with this idea, I just used my soldering skills to make inexpensive cable kits for those who cant make their own, for as cheap as I could. I mainly use these for myself but I do know a lot of hardcore software kernel developers that NEED something like this, this is my way of helping out where I can.


The headphone jack (aka TRS Connector) on the side of this Zipit Z2 is not stock. This is the modification I have made, and do offer to willing developers. If you need someone in the USA that can handle a soldering iron, PM me and we can work out details.
Posted Image

Edited by FoxxOTG, 13 September 2011 - 07:44 AM.


#3 shadowncs

shadowncs

    Newbie

  • Jr. Member
  • Pip
  • 2 posts

Posted 13 September 2011 - 10:22 PM

Hey that's looking a-good lol
Mind sharing the boot kernel message dump?

I'm thinking maybe someone with a bricked tablet can do this and then we can compare.

#4 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 15 September 2011 - 03:34 PM

Sure. This is the very first log I pulled. As you can see some of the NAND blocks were wearing out and being filed for 'retirement'. For those whom dont know, NAND Gates are used for the Flash Filesystem (same in SD card and such) and can only be re-witten to so many times before they break down. Any good NAND Flash storage will have a Wear Level and Monitor system to keep a check on the health of the gates, and stop using ones that are starting to wear out faster than others. Early day Compact Flash Cards were murdered by many ignorant people making MicroXP installs, or Mini Linux builds, and the constant writes used by the Swap/Pagefile tore the card apart really fast. This is also why when you buy a good SD card (or the like) they actually expect this and add additional storage to the unit, so when some gates start to wear, they retire it and bring in a good spare block. With crappy cards, im sure we all have seen this, we suddenly have megabytes of the card missing. This is because a gate blew out, when that happens, everything beyond that point can be un-addressable, thus, useless. Its also ok to have a few bad blocks off the factory floor, but a lot of cheap china storage devices have really *oops quality control. This is definately worth a read if you are interested in wantng more information about this topic: On MicroSD Problems - Bunnie's Blog BTW thats not my girlfriend, aka Bunnie Galore. ;} I actually get that confused A LOT in public, and its always a really awkward experience when they jeer to her "WOAH! You are the one who hacked the Xbox!!" to which she replies "No, im a nurse. I mend idiots' soldering burns after they botch a mod, while Foxx fixes it in angst." Oh and trust me I have had to repair some REALLY HORRIBLE solder jobs in my time. Where entire PCB Traces were burned off 4 layer boards.... Enjoy the log.

U-Boot 1.3.4-svn (Jun 23 2011 - 09:48:17) for SMDKC110 B Type



CPU: S5PC110@1000MHz(OK)

APLL = 1000MHz, HclkMsys = 200MHz, PclkMsys = 100MHz

MPLL = 667MHz, EPLL = 80MHz

HclkDsys = 166MHz, PclkDsys = 83MHz

HclkPsys = 133MHz, PclkPsys = 66MHz

SCLKA2M = 200MHz

Serial = CLKUART

Board: SMDKC110

DRAM: 336 MB

Flash: 1 MB

SD/MMC: 7580 MB

OneNAND:
Muxed OneNAND 512MB 1.8V 16-bit (0x50)

OneNAND version = 0x013e

Scanning device for bad blocks

Bad eraseblock 629 at 0x09d40000

Bad eraseblock 635 at 0x09ec0000

Bad eraseblock 644 at 0x0a100000

Bad eraseblock 769 at 0x0c040000

Bad eraseblock 824 at 0x0ce00000

OneNAND: 512 MB

onenand_wait: controller error = 0x0400

onenand_read_oob_nolock: read failed = 0xfffffffb

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

Partially written block 876 being set for retirement

**>> Block 876 retired

Block 876 is in state 9 after gc, should be erased

------check_poweron is 0!

------check_poweron is 0!

------check_poweron is 0!

------check_poweron good now!


OneNAND read: offset 0x80000, size 0x200000

Main area read (8 blocks):

2097152 bytes read: OK

*** Warning - using default environment


In: serial

Out: serial

Err: serial

checking mode for fastboot ...

Hit any key to stop autoboot: 0


OneNAND read: offset 0x600000, size 0x400000

Main area read (16 blocks):

4194304 bytes read: OK


OneNAND read: offset 0xb00000, size 0x180000

Main area read (6 blocks):

1572864 bytes read: OK

Boot with zImage

get_format

-------- 1 --------

## Loading init Ramdisk from Legacy Image at 30a00000 ...

Image Name: ramdisk

Created: 2011-07-05 3:42:18 UTC

Image Type: ARM Linux RAMDisk Image (uncompressed)

Data Size: 1299203 Bytes = 1.2 MB

Load Address: 30800000

Entry Point: 30800000

Verifying Checksum ... OK


Starting kernel ...


Uncompressing Linux............................................................................................................................................................................................................... done, booting the kernel.
Initializing cgroup subsys cpu
Linux version 2.6.32.9 (root@caixl-desktop) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #397 PREEMPT Mon Jun 20 10:15:23 CST 2011
CPU: ARMv7 Processor [412fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: SMDKC110
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x00000000
Ignoring unrecognised tag 0x41001099
Memory policy: ECC disabled, Data cache writeback
Normal zone: 1 pages exceeds realsize 0
CPU S5PV210/S5PC110 (id 0x43110221)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
mout_mmc: bad source 15
copy: bad source 0
mout_audss: bad source 0
S5PV210: PLL settings, A=1000000000, M=667000000, E=80000000
s5pv210: 37748736 bytes system memory reserved for mfc at 0x30b3e000
s5pv210: 37748736 bytes system memory reserved for mfc at 0x40204000
s5pv210: 14680064 bytes system memory reserved for fimc0 at 0x42604000
s5pv210: 3145728 bytes system memory reserved for fimc1 at 0x43404000
s5pv210: 6291456 bytes system memory reserved for fimc2 at 0x43704000
s5pv210: 5132288 bytes system memory reserved for jpeg at 0x32f3e000
s5pv210: 10485760 bytes system memory reserved for texstream at 0x33423000
s5pv210: 3145728 bytes system memory reserved for fimd at 0x43d04000
s5pv210: 8388608 bytes system memory reserved for g2d at 0x33e23000
Built 3 zonelists in Zone order, mobility grouping on. Total pages: 121666
Kernel command line: console=ttySAC2,115200 init=/linuxrc no_console_suspend fbcon=rotate:2
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 95MB 256MB 128MB = 479MB total
Memory: 353272KB available (5004K code, 1492K data, 520K init, 0K highmem)
SLUB: Genslabs=9, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=4
Hierarchical RCU implementation.
NR_IRQS:339
VIC @f4000000: id 0x00041192, vendor 0x41
VIC @f4010000: id 0x00041192, vendor 0x41
VIC @f4020000: id 0x00041192, vendor 0x41
vic_pm_register: too few VICs, increase CONFIG_ARM_VIC_NR
VIC @f4030000: id 0x00041192, vendor 0x41
vic_pm_register: too few VICs, increase CONFIG_ARM_VIC_NR
mult[140737]
max_delta_ns[2147483647]
min_delta_ns[30517]
rate[32768]
HZ[256]
Console: colour dummy device 80x30
console [ttySAC2] enabled
Calibrating delay loop... 996.00 BogoMIPS (lpj=1945600)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
regulator: core version 0.5
NET: Registered protocol family 16
S5PC110 Hardware version : EVT1
S3C Power Management, Copyright 2004 Simtec Electronics
S5PV210 Power Domain API Enable
S5PV210: Initializing architecture
s3c24xx-pwm s3c24xx-pwm.0: tin at 4168750, tdiv at 4168750, tin=divclk, base 0
s3c24xx-pwm s3c24xx-pwm.1: tin at 8337500, tdiv at 8337500, tin=divclk, base 8
s3c24xx-pwm s3c24xx-pwm.2: tin at 4168750, tdiv at 4168750, tin=divclk, base 12
s3c24xx-pwm s3c24xx-pwm.3: tin at 4168750, tdiv at 4168750, tin=divclk, base 16
bio: create slab <bio-0> at 0
s3c-i2c s3c2410-i2c.0: slave address 0x10
s3c-i2c s3c2410-i2c.0: bus frequency set to 65 KHz
s3c-i2c s3c2410-i2c.0: i2c-0: S3C I2C adapter
s3c-i2c s3c2410-i2c.1: slave address 0x10
s3c-i2c s3c2410-i2c.1: bus frequency set to 81 KHz
s3c-i2c s3c2410-i2c.1: i2c-1: S3C I2C adapter
s3c-i2c s3c2410-i2c.2: slave address 0x10
s3c-i2c s3c2410-i2c.2: bus frequency set to 65 KHz
s3c-i2c s3c2410-i2c.2: i2c-2: S3C I2C adapter
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Bluetooth: Core ver 2.15
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Switching to clocksource clock_source_systimer
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 6, 327680 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 1268K
[ JACK_DRIVER (sec_jack_init,832) ]
SEC JACK: Registering jack driver
input: sec_jack as /devices/virtual/input/input0
[ JACK_DRIVER (sec_jack_probe,701) ] registering switch_sendend switch_dev sysfs sec_jack
[ JACK_DRIVER (detect_irq_handler,407) ] jack isr
[ JACK_DRIVER (detect_irq_handler,407) ] jack isr
[ JACK_DRIVER (sec_jack_probe,758) ] det isr det=0Xbe, ret =0
[ JACK_DRIVER (jack_detect_change,298) ]
JACK dev detached 0
S5PV210 ADC driver, © 2010 Samsung Electronics
cpuidle: phy_regs_save:0x359e0000
------------pix_i2c register dev success
Loaded driver for PL330 DMAC-0 s3c-pl330
DBUFF-64x8bytes Num_Chans-8 Num_Peri-2 Num_Events-32
Loaded driver for PL330 DMAC-1 s3c-pl330
DBUFF-8x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
Loaded driver for PL330 DMAC-2 s3c-pl330
DBUFF-8x4bytes Num_Chans-8 Num_Peri-32 Num_Events-32
NetWinder Floating Point Emulator V0.97 (extended precision)
ashmem: initialized
ROMFS MTD © 2007 Red Hat, Inc.
msgmni has been set to 693
alg: No test for stdrng (krng)
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
i2c /dev entries driver
i2c-gpio i2c-gpio.3: using pins 14 (SDA) and 15 (SCL)
i2c-gpio i2c-gpio.4: using pins 125 (SDA) and 126 (SCL)
i2c-gpio i2c-gpio.12: using pins 18 (SDA) and 19 (SCL)
i2c-gpio i2c-gpio.8: using pins 16 (SDA) and 17 (SCL)
i2c-gpio i2c-gpio.7: using pins 214 (SDA) and 215 (SCL)
i2c-gpio i2c-gpio.9: using pins 212 (SDA) and 213 (SCL)
Linux video capture interface: v2.00
IPC probe success
mfc_init: <6>S5PC110 MFC Driver, © 2009 Samsung Electronics

S3C JPEG Driver, © 2007 Samsung Electronics
JPEG driver for S5PV210
i2c i2c-1: attached s5p_ddc into i2c adapter successfully
S5PC11X HPD Driver, © 2009 Samsung Electronics
S5PC11X CEC Driver, © 2009 Samsung Electronics
max8698_ldo_enable[246] ldo 2
regulator: LDO2: 1100 mV
max8698_ldo_enable[246] ldo 3
regulator: LDO3: 1100 mV
max8698_ldo_enable[246] ldo 4
regulator: LDO4: 3300 mV
max8698_ldo_enable[246] ldo 5
regulator: LDO5: 3300 mV
regulator: LDO6: 1800 mV
max8698_ldo_enable[246] ldo 7
regulator: LDO7: 3300 mV
max8698_ldo_enable[246] ldo 8
regulator: LDO8: 3300 mV
regulator: LDO9: 3000 mV
max8698_ldo_enable[246] ldo 10
regulator: BUCK1: 750 <--> 1500 mV
max8698_ldo_enable[246] ldo 11
regulator: BUCK2: 950 <--> 1200 mV
regulator: BUCK3: 1800 mV
s3cfb_probe
s3cfb s3cfb: [fb2] dma: 0x43d04000, cpu: 0xe9400000, size: 0x002ee000
fbcon: s3cfb (fb0) is primary device
Console: switching to colour frame buffer device 100x30
FIMD src sclk = 133400000
s3cfb s3cfb: vclk(34635000) should be smaller than 33000000
s3cfb s3cfb: vclk(33350000) should be smaller than 33000000 Hz
parent clock: 133400000, vclk: 33000000, vclk div: 4
s3cfb s3cfb: registered successfully
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
s5pv210-uart.0: s3c2410_serial0 at MMIO 0xe2900000 (irq = 16) is a S3C6400/10
s5pv210-uart.1: s3c2410_serial1 at MMIO 0xe2900400 (irq = 20) is a S3C6400/10
s5pv210-uart.2: s3c2410_serial2 at MMIO 0xe2900800 (irq = 24) is a S3C6400/10
s5pv210-uart.3: s3c2410_serial3 at MMIO 0xe2900c00 (irq = 28) is a S3C6400/10
brd: module loaded
loop: module loaded
Muxed OneNAND 512MB 1.8V 16-bit (0x50)
OneNAND version = 0x013e
Scanning device for bad blocks
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 629 at 0x09d40000
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 635 at 0x09ec0000
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 644 at 0x0a100000
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 769 at 0x0c040000
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 824 at 0x0ce00000
onenand_bbt_wait: ecc error = 0xaaaa, controller error 0x0400
Bad eraseblock 876 at 0x0db00000
Creating 8 MTD partitions on "<NULL>":
0x0000000c0000-0x000000100000 : "misc"
0x000000100000-0x000000600000 : "recovery"
0x000000600000-0x000000b00000 : "kernel"
0x000000b00000-0x000000e00000 : "ramdisk"
0x000000e00000-0x000008600000 : "system"
0x000008600000-0x000009a00000 : "backup"
0x000009a00000-0x00000ea00000 : "cache"
0x00000ea00000-0x000020000000 : "userdata"
PPP generic driver version 2.4.2
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
s3c_udc_probe
s3c-udc : S3C HS USB OTG Device Driver, © 2008-2009 Samsung Electronics
s3c-udc : version 15 March 2009 (DMA Mode)
android init
android_probe pdata: c05d2280
android_bind
android_usb gadget: android_usb ready
Registered gadget driver 'android_usb'
f_adb init
android_register_function adb
f_mass_storage init
android_register_function usb_mass_storage
mass_storage_bind_config
fsg_probe pdata: c05d22a4
android_usb gadget: Number of LUNs=2
adb_bind_config
mice: PS/2 mouse device common for all mice
input: m3g-keypad as /devices/virtual/input/input1
m3g_keypad_open
release power
input: nastech-tk as /devices/platform/i2c-gpio.3/i2c-3/3-0046/input/input2
---------------nastech_tk_checkonline----success!
nastech IT7235 touchscreen key driver sucess!
input: Goodix-TS as /devices/platform/i2c-gpio.4/i2c-4/4-0055/input/input3
--------------goodix_ts_init_hw success!
Goodix-TS 4-0055: Guitar Version: GT801_1R06_2011031601_Goodix_Tech
GOODIX GT801 touchscreen driver sucess!
bma150 7-0038: bma150 found
bma150 7-0038: al_version=2, ml_version=1
input: accelerometer as /devices/virtual/input/input4
input: geomagnetic as /devices/platform/i2c-gpio.9/i2c-9/9-002e/input/input5
input: geomagnetic_raw as /devices/platform/i2c-gpio.9/i2c-9/9-002e/input/input6
input: orientation as /devices/virtual/input/input7
S3C24XX RTC, © 2004,2006 Simtec Electronics
using rtc device, s3c, for alarms
s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
M3G ADC battery Driver probe success!!!
ibcow_init: ibcom ow module init
S3C2410 Watchdog Timer, © 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq enabled
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com
Bluetooth: Virtual HCI driver ver 1.3
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCILL protocol initialized
cpuidle: using governor ladder
cpuidle: using governor menu
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright© Pierre Ossman
s3c-sdhci s3c-sdhci.0: clock source 2: sclk_mmc (47642857 Hz)
MMC e_unknown
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA
s3c-sdhci s3c-sdhci.1: clock source 2: sclk_mmc (47642857 Hz)
MMC e_unknown
mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
usbcore: registered new interface driver usbhid
usbhid: v2.6:USB HID core driver
logger: created 64K log 'log_main'
logger: created 256K log 'log_events'
logger: created 64K log 'log_radio'
logger: created 64K log 'log_system'
Advanced Linux Sound Architecture Driver Version 1.0.21.
s3c_idma_preallocate_buffer: VA-e8900000 PA-C0000000 163840bytes
s3c_preallocate_dma_buffer: VA-ff005000, PA-352A0000, 131072bytes
asoc: AK4671 <-> s3c64xx-i2s mapping ok
mmc_rescan mmc0, search for SDIO
ALSA device list:
#0: smdkc110 (AK4671)
mmc_rescan mmc0, search for SD
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.14
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.6
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
OV7670 8-0021: ov7670 has been probed
OV7670 8-0021: fetching platform data
OV7670 8-0021: parallel mode
FIMC0 registered successfully
FIMC1 registered successfully
FIMC2 registered successfully
S5PC1XX TVOUT Driver, © 2009 Samsung Electronics
s5p-tvout s5p-tvout: hpd status is cable removed
regulator_init_complete: incomplete constraints, leaving VCC_MEM on
regulator_init_complete: incomplete constraints, leaving {VADC/VSYS/VKEY}_2.8V on
regulator_init_complete: incomplete constraints, leaving VCC_1.8V on
regulator_init_complete: incomplete constraints, leaving VMMC_2.8V/VEXT_2.8V on
s3c2410-rtc s3c2410-rtc: hctosys: invalid date/time
Freeing init memory: 520K
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SU08G 7.40 GiB
mmcblk0: p1
PA FB = 0x43D04000, bits per pixel = 32
screen width=800 height=480 va=0xd3d04000 pa=0x43d04000
Back frameBuffer[0].VAddr=d3e7b000 PAddr=43e7b000 size=1536000
mmc_rescan mmc1, search for SDIO
mmc_rescan mmc1, search for SD
mmc_rescan mmc1, search for MMC
yaffs: dev is 32505860 name is "mtdblock4" rw
yaffs: passed flags ""
yaffs: dev is 32505863 name is "mtdblock7" rw
yaffs: passed flags ""
yaffs: dev is 32505862 name is "mtdblock6" rw
yaffs: passed flags ""
onenand_wait: ECC error = 0xaaaa
onenand_wait: ECC error = 0xaaaa
onenand_wait: ECC error = 0xaaaa
onenand_wait: ECC error = 0xaaaa
onenand_wait: ECC error = 0xaaaa
onenand_wait: ECC error = 0xaaaa
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s5pv210-ohci s5pv210-ohci: s5pv210 OHCI
s5pv210-ohci s5pv210-ohci: new USB bus registered, assigned bus number 1
s5pv210-ohci s5pv210-ohci: irq 87, io mem 0xec300000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
sh: can't access tty; job control turned off
# init: cannot find '/system/bin/usb_modeswitch', disabling 'usbmodeswitch'
init: cannot find '/system/bin/3gd', disabling '3gd'
enabling adb
warning: `rild' uses 32-bit capabilities (legacy support in use)
adb_open
PVR_K:(Warning): SysFinalise: Version string: SGX540 S5PC110 [473, services4/system/s5pc110/sysconfig.c]
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0x2
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0x9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
SND_SOC_AK4671 out3 speaker power down
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0xa
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0xa9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
SND_SOC_AK4671 out3 speaker power down
s3c-fimc: FIMC2 1 opened.
request_suspend_state: wakeup (3->0) at 20270903105 (1970-01-01 00:00:20.270899063 UTC)
[WIFI] Device powering ON
[WIFI] WIFI_REG_ON = 1
[WIFI] WIFI_RST = 1
MMC e_inserting

Dongle Host Driver, version 4.218.243.1
mmc_rescan mmc1, search for SDIO
mmc1: new SDIO card at address 0001
DHD: dongle ram size is set to 294912(orig 294912)
Firmware version = wl0: Aug 11 2010 13:21:21 version 4.218.243.1
eth0: Broadcom Dongle Host Driver mac=78:d6:f0:25:f9:af
Enter wl_control_wl_start
Exited wl_control_wl_start
Unkown PRIVATE command, ignored
Unkown PRIVATE command, ignored
Unkown PRIVATE command, ignored
Unkown PRIVATE command, ignored
Unkown PRIVATE command, ignored
Unkown PRIVATE command, ignored
STA connect received 1
Unkown PRIVATE command, ignored
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0xa
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0xa9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
SND_SOC_AK4671 out3 speaker power down
press vol up
release vol up
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0xa
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0xa9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
press vol down
release vol down
press vol down
release vol down
press vol up
release vol up
SND_SOC_AK4671 out3 speaker power down
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0xa
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0xa9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
init: untracked pid 2323 exited
init: untracked pid 2528 exited
dhd_osl_detach: MEMORY LEAK 2048 bytes
[WIFI] Device powering OFF
[WIFI] WIFI_RST = 0
MMC e_inserted
mmc1: card 0001 removed
mmc_rescan mmc1, search for SDIO
mmc_rescan mmc1, search for SD
mmc_rescan mmc1, search for MMC
SND_SOC_AK4671 out3 speaker power down
press power
release power
IIS Audio: 16Bits Stereo 44100Hz
HW Param read reg[0x18] = 0xa
HW Param write reg[0x50] = 0x0
HW Param write reg[0x51] = 0x93
HW Param write reg[0x52] = 0xa9
DmaAddr=@c0000000 Total=32768bytes PrdSz=8192 #Prds=4 dma_area=0xe8900000
LOUT3 write reg[0x50] = 0xac
LOUT3 write reg[0x51] = 0xab
LOUT3 write reg[0x52] = 0xab
Power down.
smdkv210_power_off : setting GPIO_P



#5 shadowncs

shadowncs

    Newbie

  • Jr. Member
  • Pip
  • 2 posts

Posted 16 September 2011 - 08:46 PM

No, im a nurse


I see no reason why a nurse can't hack an Xbox. So I'm not convinced :)

Regarding the log, it's kind of weird with those bad blocks... especially since OneNAND should be this high reliability thing with internal error correction. As long as they don't grow I guess everything is fine (but I'm not an expert).

So U-boot loads 3 chunks from the flash:

OneNAND read: offset 0x80000, size 0x200000 (2MB)
OneNAND read: offset 0x600000, size 0x400000 (4MB)
OneNAND read: offset 0xb00000, size 0x180000 (1.5MB)

The last one is probably the ramdisk (or kernel+ramdisk?) of 1.5MB. We get a message lower about a ramdisk of 1.2MB which would fit this.

Some weird messages about s5pv210 (Dropad A8 board) - Probably just a reused piece of code or subsystem.

So that would be a reference dmesg. I wonder if the flash failed for some of the people that are having issues.

#6 perimbean

perimbean

    Member

  • Jr. Member
  • PipPip
  • 11 posts

Posted 20 September 2011 - 08:17 PM

Hi!
I'm interested to find out how to de-brick or reset the A8X should I load a custom rom/kernel and resulting in the bricking of the A8X.

I've searched the net and there is no actually any developer tool (universal) enough to "reset/reboot" the A8X.

I'm keen to learn how to do up the addon and use serial console to "talk" to A8X.

Please advise.

Thanks!

#7 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 22 October 2011 - 12:23 PM

If you are new to serial ports and debug consoles, I did a 2 part series explaining it on my show. http://www.BSoDtv.org Episodes 31 and 32, 'Serial Communication'. Once you understand the core concepts, it's not too hard. I think the most confusing part for most people are the port voltage level converters, which many USB Serial Bridge cables will do for you, and the port settings. Most gizmos today dont run at 12V RS-232 voltage levels, that's not much to worry about. The Dropad (and seems to be the default over the years) port settings is 115.2K 8N1. Being this is a simple 3-Wire serial port there is no flow control. Once you solder leads from the dropad serial port (cross-talk, meaning dropad transmit leads into computer receive, and vice-versa). I use headphone jacks because they have been used this way since the 80s', are just the right number of pins, cant plug them in backwards or wrong, and are very easy to get. Load up your serial terminal software, set the port speed and flow settings, and turn on (or hit reset) on your dropad. uBoot should quickly come to life. Here is my latest uBoot log file:

http://pastebin.com/2Rrzx3Sb

PM me or catch me on BSoD IRC (check the site for server info) and feel free to ask for help or advice if you need.


P.S.
If you are keen on experimenting before putting your dropad in for surgery, you can buy two inexpensive USB Serial bridge cables like the ones I have, cross them together, open two instances of your terminal software. Window 1 is set to talk to USB Serial Adapter A, the other Window 2 is set to talk to Serial Adapter B. This will set up two USB serial ports on the same host that cross talk between eatch other as separate hardware. This way its like playing with your cell phone by calling it from your home phone. Everything is isolated in a safe neutral environment where nothing can break or blow up. I also have some tips on getting these cables for cheap by knowing exactly what to search for online.

Edited by FoxxOTG, 22 October 2011 - 12:35 PM.


#8 freshdroider

freshdroider

    Newbie

  • Jr. Member
  • Pip
  • 4 posts

Posted 18 November 2011 - 10:43 PM

hi FoxxOTG, I warched your episodes regarding rs232 ports and debugging and followed your instructions as best I could but my hyperterminal does not show anything when I connect and press the power button on my dropad a8x.
I'm using a prolific usb to serial adapter on win7, made a null modem cable with loop back handshake and connected using 115.2 8n1. I tried Xon/Xoff, hardware and no flow control but still nothing.

My original issue was that someone had flashed an updated firmware from saayi then it wouldn't boot passed the dropad logo. I then managed to get it to reflash from sd card. the flash completed then it went dead. now it does nothing other than show the charging light when plugged in. I can hear that windows finds a device if I keep the power button in and it loses the device when I release the button.

Any ideas?

Thanks

#9 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 19 November 2011 - 12:57 PM

Try to use Realterm to connect to the dropad. I use a simple 3-wire cable with no null modem loopack. Just a 3-wire setup with no flow control, your 115k 8n1 settings are correct. Plug in the serial, open the terminal, connect to the port (also called Opening the Port) and press power on the a8x. It should instantly show that you pressed the power button. If it doesnt start to boot, hold the power for a few seconds. Of course make sure you have your battery charged when you do this. If there is nothing on your terminal screen when you press the power button, either something is wrong with the terminal, or your dropad. You can test the serial by crossing RX and TX together while the port is open and connected. Anything you type should shoot out of TX and come right back via RX and display on your terminal screen.

You can also use PuTTY to connect via serial if hyeperterminal and Realterm give you any crap. What are you using for the serial port and connection? Are you sure your serial port is working at the needed 3.3v logic level?

#10 Kasbert

Kasbert

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 33 posts

Posted 20 November 2011 - 06:08 AM

I soldered the wires for serial port and managed to get data from the serial port but it is all garbled. The junk seem to be systematic (I got the same output with different speeds), so I guess the serial port pins are inverted, compared to what s5pc110 expects. I am using a pl2303 based USB serial adapter (search for sku24799), a cheap one that does not have RS-232 level converter.

#11 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 21 November 2011 - 01:27 PM

I soldered the wires for serial port and managed to get data from the serial port but it is all garbled. The junk seem to be systematic (I got the same output with different speeds), so I guess the serial port pins are inverted, compared to what s5pc110 expects. I am using a pl2303 based USB serial adapter (search for sku24799), a cheap one that does not have RS-232 level converter.


The PL2303 should have an onboard level shifter that works in the 3.3V range just fine. At first I didnt get anything from the port but it turned out I had a bad connection. Once I fixed it up it worked flawlessly. Im not using a cheap china knockoff cable either, but it's not an expensive one either. I have had some weirdness with various terminal software not having proper character translation, putting garbage data on the display now and again, mainly with LF, NULL, and CR ANSI though.

#12 Kasbert

Kasbert

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 33 posts

Posted 22 November 2011 - 01:37 PM

The PL2303 should have an onboard level shifter that works in the 3.3V range just fine. At first I didnt get anything from the port but it turned out I had a bad connection. Once I fixed it up it worked flawlessly. Im not using a cheap china knockoff cable either, but it's not an expensive one either. I have had some weirdness with various terminal software not having proper character translation, putting garbage data on the display now and again, mainly with LF, NULL, and CR ANSI though.


I added a 74L14 inverter and now I am getting some bootlog and I can stop the autoboot to get u-boot prompt. During U-Boot it is randomly dropping characters.

U-Bot 13.4-vn (Jl 282011  14:0:04)for MDKC10 B ype

CU:  SPC11@1000Hz(O)
      APLL  100MHz, clkMys = 00MH, PclMsys= 100Hz
MPLL  667Hz, ELL      clkDys = 66MH, PclDsys= 83Hz
              HclPsys= 133Hz,PclkPss =66MHz
                                                              SLKAM  = 20MH
Seril =CLKUAR
oard:  SMKC110
              DRA:    36 M
Flas:  1 MB
D/MMC  1886MB
Mxed OeNAN 512M 1.8 16-bt (050)
neNAD vesion  0x03e
Sannng devce or badbloks
Ba ersebloc 87 at 0xdb80000
Baderasebock1168 a 0x240000
OneNAD: 52 MB
-----chec_powron i 0!
-----chek_powron ood nw!

neNND red: ofset x8000, sie 0x0000
Mai are read(8 bocks)
** Warnng  usingdefult eniroment
Out    serial
Er:    seril
checing ode fr fatboot...
Hitany ey tostopautobot:  0
However, when the kernel starts, it stops dropping characters.
OeNANDread offst 0x00000 siz 0x40000
 19404 byts rad: OK                 Main rea ead (6 blcks):
Mainarearead(6 blcks)000 sie 0x10000
 172864byte read OK
Bootwit zImag
-------  -------
                ## LadinginitRamdik frm Leacy Iage t 30a000 ...
  Iage Nae:  ramdik
  Creaed:     211-9-17  2:4:59 UT
  ImageTyp:   AR Liux RAMiskImage uncmpresed)
                                                Daa Sie:   14245 Byes = 39.1kB
  Loa Addrss: 080000
  Entr Poit:  380000
  Veriying heckum .. K

tartng kenel ..

Unompresin Linux.. dne, ootin thekerne.
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 2.6.35.7 (root@andy-Work-PC) (gcc version 4.4.1 (S1
[    0.000000] CPU: ARMv7 Processor [412fc082] revision 2 (ARMv7), cr=10c53c7f
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction ce
[    0.000000] Machine: SMDKC110
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Ignoring unrecognised tag 0x41001099
...

I am using minicom on a Linux box.

Edited by Kasbert, 22 November 2011 - 02:33 PM.


#13 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 23 November 2011 - 08:11 PM

I mentioned in my reply-post in Dropad Hardware where we have been working on the SD Boot stuff, I dont think the 74L14 can handle 3.3V. I used it on an LPC Flash programmer a few years back which operates at 3.3V and I had a similar issue. The 74L14 is 5V (4.5V minimal - I switched to a 74H14 (or the 74HC14 which can operate at I think 2.8v minimal) and it worked out for me.

I wonder why you need to invert your data lines. If you have a windows machine try out RealTerm. The software has the option to invert the data, though with my PL2303 cable I dont need to use this option. Feel free to PM me if you need more advice.

#14 freshdroider

freshdroider

    Newbie

  • Jr. Member
  • Pip
  • 4 posts

Posted 27 December 2011 - 05:44 PM

Try to use Realterm to connect to the dropad. I use a simple 3-wire cable with no null modem loopack. Just a 3-wire setup with no flow control, your 115k 8n1 settings are correct. Plug in the serial, open the terminal, connect to the port (also called Opening the Port) and press power on the a8x. It should instantly show that you pressed the power button. If it doesnt start to boot, hold the power for a few seconds. Of course make sure you have your battery charged when you do this. If there is nothing on your terminal screen when you press the power button, either something is wrong with the terminal, or your dropad. You can test the serial by crossing RX and TX together while the port is open and connected. Anything you type should shoot out of TX and come right back via RX and display on your terminal screen.

You can also use PuTTY to connect via serial if hyeperterminal and Realterm give you any crap. What are you using for the serial port and connection? Are you sure your serial port is working at the needed 3.3v logic level?


Hi FoxxOTG,

I've tried all sorts of terminals and all give the same result, nothing. When I short the TX and RX I get my input returned via the terminal so the serial connection seems to be working but the dropad still does not show anything in the terminal.
When I connect the dropad to my PC via USB and then press and hold the power button I can here the device being detected and I can see it in the device manager so it's not completely ruined I think.

I'm not sure how to check whether it is using the 3.3v logic level, any help with this would be appreciated.

Thanks for your help.

Cheers,

#15 FoxxOTG

FoxxOTG

    Advanced Member

  • Jr. Member
  • PipPipPip
  • 80 posts

Posted 28 December 2011 - 10:17 PM

Well thats quite odd.

What is the chipset for your USB Serial Bridge? If you are running a Windows OS check in "Device Manager" under "Com Ports" and look in the "Device Properties" perhaps in the Driver Details section if my memory serves me correct, it should tell you if its a Prolific, FTDI, or other brand. Under linux console try the command lsusb and it should tell you the vendor. I can try to look up the hardware and see if its 3.3v Logic tolerant. prolific tends to hold the best compatibility for 3.3V devices for me, FTDI has better 5V Logic tolerances, it can work with 3.3V levels but sometimes it just doesnt work right.