Jump to content

Search the Community

Showing results for tags 'boot'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Events/Announcements
    • General Discussion
  • General
    • Learning Center
    • Linksprite Operating System Images
    • General Discussion
  • LinkSprite pcDuino
    • Bug Report
    • General Discussions
    • pcDuino9S
    • pcDuino9 Mini and Kit
    • pcDuino Lite Wifi
    • pcDuino Lite
    • pcDuino1/2
    • pcDuino3
    • pcDuino3S
    • pcDuino8 Uno
    • Android
    • Ubuntu
    • Programming
    • Community
    • Arches General Discussion
    • Acadai General Discussion
  • LinkNet
    • ONetSwitch
  • Camera
    • JPEG Camera
  • RFID
    • Integrated UHF Far Distance Readers
    • Cottonwood UHF RFID Reader
    • NFC RFID
  • Powerline Communication
    • Spyder
    • PLC with SimpleMAC
    • McLaren
    • Mamba
  • Arduino Shields
    • General Discussions
    • 16x2 LCD Shield
    • Anaconda WiFi Shield
    • Bluetooth Shield
    • CuHead Pro With Airplay/DLNA Shield
    • GSM/GPRS/3G Cellular Shields
    • GPS SD Shield
    • CuHead/Diamondback/RedBack WiFi
    • RS 485 Shield
    • Touch LCD Shield
    • Linker Kit
  • Deepcam
    • General Discussions
    • SDK Support
  • LinkNode
    • D1 ESP8266 Arduino Compatible
    • BLE 4.0 Mbed compatible sensor tag
    • DIY GPS Tracker
    • Weather Station
  • PetKollar
    • General Discussions
  • Wireless, GPS, Cellular
    • WiFi
    • GPS
  • Robotics
    • General Discussions
    • Rover
  • Raspberry Pi
    • RS232/GPIO Shield for Raspberry Pi
    • RS485/GPIO Shield for Raspberry Pi
  • STEM Education
    • General Discussion
  • Projects
    • General Discussions
    • Gaming
    • OpenCV/SimpleCV
    • Networking and Servers
    • Media Centers
    • Robotics
    • CNC
    • Lighting
    • Virtual Reality
    • Internet of Things
  • Sourcing with LinkSprite
    • General Discussion

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 11 results

  1. LS-Support-12

    Is it booted from SD or NAND?

    I have seen this link. However, after cloning NAND to SD and restarting, my result of 'df -h' is different from both photos in the tutorial (my output is here). I think that my pcDuino booted from SD. I have two reasons. First one is that /dev/mmcblk0p1 is listed on the output of 'df -h'. Other reason is that when I run board-config.sh, I have no option to clone my system to SD card anymore. However, I would like to hear your opinion, is it booted from SD or NAND? Also, why the output I have is different from both outputs in the tutorial?
  2. Dear All .. My friend give me his board. I don't know the condition. I think it's PCDUINO3 , since it's looks like http://www.linksprite.com/?page_id=812 I Plug my UART to USB, and got : And I try to use kernel image from https://s3.amazonaws.com/pcduino/Images/v3/20140721/pcduino3_a20_kernel_dd_20140721.img But I got Kindly please tell me how to fix this Sincerely -bino-
  3. I just bought an Acadia 3.0 production board and wanted to know if I can boot it from the SATA hard disk? Also, I wanted to move the MicroSD image to the the SATA disk, but when I do SYNC it hangs. Any ideas? Thanks
  4. I am trying to burn the Lubuntu 14 NAND image using Ubuntu with dd method. I manage to burn it successfully. After I install it (led is blinking some time and stops), it does not want to boot. Did anyone managed to install Lubuntu 14 using dd method? I am entering these commands in terminal: sudo dd if=imagelocation of=microSDlocation bs=1M My microSD card is Transcend 16GB. I manage to install Ubuntu 12 using dd and Lubuntu 14 using Windows, so the memory card looks fine.
  5. I am trying to boot the Acadia from either image (SD boot or eMMC boot) using the instructions here. 1. SD Boot Booting from SD card works initially but hangs with the message: 2. eMMC Boot Nothing happens. As it turns out, the hardware version I have (Acadia 1 V3.0) does not have configuration switches (the DIP switches just above the CPU are not populated). This makes following the guides (specifically the parts about setting the DIP switches to configure eMMC boot) a little difficult. Please help! I cannot get the Acadia to do anything at this point.
  6. In order to mount some specific device on particular location every time, firstly determine the uuid of the device, which is unique for it. You can do it by typing in terminal: ls -al /dev/disk/by-uuid/ After executing this, you will probably see multiple uuids for different devices. Experiment with your device (USB, microSD) by ejecting it, executing the command again, and then again plugging it in pcDuino, until you determine its specific uuid. After you know it, execute the following to mount it: sudo mount /dev/disk/by-uuid/YOURUUID /YOUR/SPECIFIC/LOCATION Note: Replace YOURUUID with uuid of your device and /YOUR/SPECIFIC/LOCATION with full path of the directory you want to mount this particular device to. If the upper commands work and you manage to mount your device this way, then you can simply add it to the startup commands. After that, it should be mounted on the location you specified on every boot (as long as it is inside and you do not format it, since the format could change the uuid).
  7. LS-Support-12

    pcDuino3 no HDMI signal

    I am experiencing really weird behavior of my pcDuino 3. Everything was working perfectly. Suddenly, I cannot get HDMI signal from it to my monitor. When I power cycle it, I see the pcDuino logo and then monitor is going in stand by mode (every time), which means there is no signal from pcDuino. However, pcDuino continues to boot (since I see leds (e.g. TX, RX, LED2) on after it). I tried reflashing. I tried Android image and Lubuntu 14 image. Everything is the same. What is, probably, the most significant is that when I put Lubuntu 12 on my pcDuino (since it will connect to the internet automatically when you put LAN cable in it) I am able to see the IP address on my router and even SSH to it, which definitely means it is on and working. However, no output on the monitor again. I have not been doing anything unusual with it and it was working perfectly last time when I was using it. Please, tell me what you think. Have you experienced something like this before and what do you think it could be the issue?
  8. Brad.Haber

    S3C6410 Board

    I have a S3C6410 board that I can't get to boot. Is there anyone on this forum that has experience using this board that may be able to help me figure out what to do? This is the output from the DNW app that comes with the kit. OK U-Boot 1.1.6 (Jan 4 2011 - 21:24:28) for SMDK6410 CPU: S3C6410@800MHz Fclk = 800MHz, Hclk = 133MHz, Pclk = 66MHz, Serial = CLKUART (SYNC Mode) Board: SMDK6410 DRAM: 256 MB Flash: 0 kB NAND: Maf. ID is d3 1024 MB *** Warning - bad CRC or NAND, using default environment In: serial Out: serial Err: serial Hit any key to stop autoboot: 0 NAND read: device 0 offset 0x40000, size 0x300000 s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully 3145728 bytes read: OK Boot with zImage Starting kernel ... Uncompressing Linux...................................................................................................................................................................................... done, booting the kernel. Linux version 2.6.28.6 (figo@figo-desktop) (gcc version 4.3.2 (Sourcery G++ Lite 2008q3-72) ) #721 PREEMPT Sun Jan 2 16:59:05 CST 2011 CPU: ARMv6-compatible processor [410fb766] revision 6 (ARMv7), cr=00c5387f CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache Machine: SMDK6410 Memory policy: ECC disabled, Data cache writeback CPU S3C6410 (id 0x36410101) S3C24XX Clocks, © 2004 Simtec Electronics S3C64XX: PLL settings, A=800000000, M=532000000, E=24000000 S3C64XX: HCLKx2=266666666, HCLK=133333333, PCLK=66666666 div1: 00000555 mout_apll: source is fout_apll (1), rate is 800000000 mout_epll: source is fout_epll (1), rate is 24000000 mout_mpll: source is mpll (1), rate is 532000000 mmc_bus: source is dout_mpll (1), rate is 44333333 mmc_bus: source is dout_mpll (1), rate is 44333333 mmc_bus: source is dout_mpll (1), rate is 44333333 usb-host-bus: source is mout_epll (0), rate is 24000000 uclk1: source is dout_mpll (1), rate is 66500000 spi_epll: source is mout_epll (0), rate is 24000000 spi_epll: source is mout_epll (0), rate is 24000000 sclk_audio0: source is mout_epll (0), rate is 24000000 sclk_audio1: source is mout_epll (0), rate is 24000000 sclk_audio2: source is mout_epll (0), rate is 24000000 irda-bus: source is mout_epll (0), rate is 24000000 s3c64xx: 10485760 bytes SDRAM reserved for fimc at 0x50810000 s3c64xx: 8388608 bytes SDRAM reserved for pp at 0x51210000 s3c64xx: 8388608 bytes SDRAM reserved for tv at 0x51a10000 s3c64xx: 6291456 bytes SDRAM reserved for mfc at 0x52210000 s3c64xx: 8388608 bytes SDRAM reserved for jpeg at 0x52810000 s3c64xx: 8388608 bytes SDRAM reserved for cmm at 0x53010000 s3c64xx: 19922944 bytes SDRAM reserved for s3c-g3d at 0x53810000 Built 1 zonelists in Zone order, mobility grouping on. Total pages: 56896 Kernel command line: setenv bootargs noinitrd mem=224M console=ttySAC0 init=/init ubi.mtd=1 root=ubi0:rootfs rootfstype=ubifs PID hash table entries: 1024 (order: 10, 4096 bytes) Console: colour dummy device 80x30 console [ttySAC0] enabled Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) Memory: 224MB = 224MB total Memory: 152064KB available (5308K code, 928K data, 152K init) SLUB: Genslabs=12, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Calibrating delay loop... 797.90 BogoMIPS (lpj=1994752) Mount-cache hash table entries: 512 CPU: Testing write buffer coherency: ok net_namespace: 288 bytes NET: Registered protocol family 16 S3C6410 Power Management, © 2008 Samsung Electronics S3C6410: Initialising architecture S3C DMA-pl080 Controller Driver, © 2006-2007 Samsung Electronics Total 32 DMA channels will be initialized. SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb cfg80211: Using static regulatory domain info cfg80211: Regulatory domain: US (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) (2402000 KHz - 2472000 KHz @ 40000 KHz), (600 mBi, 2700 mBm) (5170000 KHz - 5190000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5190000 KHz - 5210000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5210000 KHz - 5230000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5230000 KHz - 5330000 KHz @ 40000 KHz), (600 mBi, 2300 mBm) (5735000 KHz - 5835000 KHz @ 40000 KHz), (600 mBi, 3000 mBm) cfg80211: Calling CRDA for country: US NET: Registered protocol family 2 IP route cache hash table entries: 2048 (order: 1, 8192 bytes) TCP established hash table entries: 8192 (order: 4, 65536 bytes) TCP bind hash table entries: 8192 (order: 3, 32768 bytes) TCP: Hash tables configured (established 8192 bind 8192) TCP reno registered NET: Registered protocol family 1 S3C64XX ADC driver, © 2008 Samsung Electronics S5P64XX ADC driver successfully probed NetWinder Floating Point Emulator V0.97 (double precision) ashmem: initialized yaffs Jan 2 2011 16:55:25 Installing. msgmni has been set to 297 alg: No test for stdrng (krng) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) S3C_LCD clock got enabled :: 133.333 Mhz video output type detect error!! Failed to allocate video RAM: -12 Trying to free already-free IRQ 62 s3c-lcd: probe of s3c-lcd failed with error -12 ledsinitialized. s3c-aes initialized S3C AES Drvier Serial: 8250/16550 driver4 ports, IRQ sharing disabled s3c6400-uart.0: s3c2410_serial0 at MMIO 0x7f005000 (irq = 16) is a S3C6400/10 s3c6400-uart.1: s3c2410_serial1 at MMIO 0x7f005400 (irq = 20) is a S3C6400/10 s3c6400-uart.2: s3c2410_serial2 at MMIO 0x7f005800 (irq = 24) is a S3C6400/10 s3c6400-uart.3: s3c2410_serial3 at MMIO 0x7f005c00 (irq = 28) is a S3C6400/10 brd: module loaded loop: module loaded nbd: registered device at major 43 pmem: 1 init logger: created 64K log 'log_main' logger: created 256K log 'log_events' logger: created 64K log 'log_radio' mcp251x_init(1063): start PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). CSLIP: code copyright 1989 Regents of the University of California. dm9000 Ethernet Driver eth0: dm9000 at ce890000,ce890004 IRQ 108 MAC: 00:22:12:34:56:90 libertas_sdio: Libertas SDIO driver libertas_sdio: Copyright Pierre Ossman console [netcon0] enabled netconsole: network logging started Linux video capture interface: v2.00 s3c-fimc: controller 0 registered successfully s3c-fimc: controller 1 registered successfully S3C6400 MFC Driver, © 2007 Samsung Electronics S3C6400 MFC Driver, © 2007 Samsung Electronics S3C PostProcessor Driver v3.12, © 2009 Samsung Electronics S3C6410 TV encoder Driver, © 2008 Samsung Electronics S3C6410 TV encoder Driver init OK. S3C6410 TV scaler Driver, © 2008 Samsung Electronics S3C6410 TV scaler Driver init OK. S3C Rotator Driver, © 2008 Samsung Electronics s3c_rotator_probe called s3c_rotator_probe success S3C JPEG Driver, © 2007 Samsung Electronics s3c-g2d: Driver loaded succesfully s3c-g2d: Module initialized. s3c-g3d: Driver loaded succesfully s3c-g3d: Module initialized. S3C CMM Driver, © 2008 Samsung Electronics Driver 'sd' needs updating - please use bus_type methods Driver 'sr' needs updating - please use bus_type methods S3C NAND Driver, © 2008 Samsung Electronics S3C NAND Driver is using hardware ECC. NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit) Creating 2 MTD partitions on "NAND 1GiB 3,3V 8-bit": 0x00400000-0x00800000 : "cramfs" 0x00800000-0x40000000 : "ubifs" UBI: attaching mtd1 to ubi0 UBI: physical eraseblock size: 262144 bytes (256 KiB) UBI: logical eraseblock size: 258048 bytes UBI: smallest flash I/O unit: 2048 UBI: VID header offset: 2048 (aligned 2048) UBI: data offset: 4096 UBI: attached mtd1 to ubi0 UBI: MTD device name: "ubifs" UBI: MTD device size: 1016 MiB UBI: number of good PEBs: 4063 UBI: number of bad PEBs: 1 UBI: max. allowed volumes: 128 UBI: wear-leveling threshold: 4096 UBI: number of internal volumes: 1 UBI: number of user volumes: 1 UBI: available PEBs: 0 UBI: total number of reserved PEBs: 4063 UBI: number of PEBs reserved for bad PEB handling: 40 UBI: max/mean erase counter: 2/1 UBI: background thread "ubi_bgt0d" started, PID 1048 spi->irq = 151 Max,Min-Speed [33333333, 130208]Hz Irq=80 IOmem=[0x7f00bfff-0x7f00b000] DMA=[Rx-33, Tx-34] usbmon: debugfs is not available ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver s3c2410-ohci s3c2410-ohci: S3C24XX OHCI s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1 s3c2410-ohci s3c2410-ohci: irq 79, io mem 0x74300000 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected 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 : S3C HS USB OTG Device Driver, © 2008-2009 Samsung Electronics s3c-udc : version 15 March 2009 (DMA Mode) android adb driver Registered gadget driver 'android_adb' mice: PS/2 mouse device common for all mice gpio-keys init input: gpio-keys as /devices/platform/gpio-keys/input/input0 S3C Touchscreen driver, © 2008 Samsung Electronics S3C TouchScreen got loaded successfully : 12 bits input: S3C TouchScreen as /devices/virtual/input/input1 S3C24XX RTC, © 2004,2006 Simtec Electronics s3c2410_rtc: tick irq 34, alarm irq 92 s3c2410-rtc s3c2410-rtc: rtc disabled, re-enabling s3c2410-rtc s3c2410-rtc: rtc core: registered s3c as rtc0 i2c /dev entries driver s3c2440-i2c s3c2440-i2c: slave address 0x10 s3c2440-i2c s3c2440-i2c: bus frequency set to 378 KHz [CAMERA]camera_attach_adapter. parent clock for camera: 266.666 MHz, divisor: 11 parent clock for camera: 266.666 MHz, divisor: 11 parent clock for camera: 266.666 MHz, divisor: 9 CAMERA TVP5150 attached successfully s3c2440-i2c s3c2440-i2c: i2c-0: S3C I2C adapter at24 0-0050: 1024 byte 24c08 EEPROM (writable) sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright© Pierre Ossman s3c-sdhci s3c-sdhci.0: clock source 0: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.0: clock source 1: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.0: clock source 2: mmc_bus (44333333 Hz) mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.0] using ADMA sdhci: card inserted. s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz) s3c-sdhci s3c-sdhci.1: clock source 2: mmc_bus (44333333 Hz) mmc1: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA sdhci: card removed. usbcore: registered new interface driver usbhid usbhid: v2.6:USB HID core driver Advanced Linux Sound Architecture Driver Version 1.0.18rc3. ASoC version 0.13.2 WM9713/WM9714 SoC Audio Codec 0.15 playback: 1, capture : 1 asoc: AC97 HiFi <-> s3c64xx-ac97 mapping ok [WM9713]Open speaker volume. ALSA device list: #0: SMDK6400 (WM9713) TCP cubic registered NET: Registered protocol family 17 can: controller area network core (rev 20081130 abi 8) NET: Registered protocol family 29 mmc1: new high speed SDHC card at address 1234 RPC: Registered udp transport module. RPC: Registered tcp transport module. ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright © 2004-2005 Intel Corporation <jketreno@linux.intel.com> VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5 mmcblk0: mmc1:1234 SA04G 3.63 GiB mmcblk0: p1 s3c2410-rtc s3c2410-rtc: setting system clock to 2000-10-30 01:42:57 UTC (972870177) s3c-nand: 1 bit(s) error detected, corrected successfully UBIFS: recovery needed UBIFS: recovery completed UBIFS: mounted UBI device 0, volume 0, name "rootfs" UBIFS: file system size: 1034256384 bytes (1010016 KiB, 986 MiB, 4008 LEBs) UBIFS: journal size: 33546240 bytes (32760 KiB, 31 MiB, 130 LEBs) UBIFS: media format: 4 (latest is 4) UBIFS: default compressor: LZO UBIFS: reserved for root: 5182151 bytes (5060 KiB) VFS: Mounted root (ubifs filesystem). Freeing init memory: 152K s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully Warning: unable to open an initial console. s3c-nand: 1 bit(s) error detected, corrected successfully init: cannot open '/initlogo.rle' eth0: link down s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully sh: can't access tty; job control turned off # s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully warning: `rild' uses 32-bit capabilities (legacy support in use) s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully s3c-nand: 1 bit(s) error detected, corrected successfully request_suspend_state: wakeup (3->0) at 26416918775 (2000-10-30 01:43:17.054911732 UTC) init: untracked pid 1984 exited request_suspend_state: wakeup (0->0) at 37246996909 (2000-10-30 01:43:27.884989895 UTC) init: untracked pid 2031 exited request_suspend_state: wakeup (0->0) at 47894773046 (2000-10-30 01:43:38.532765867 UTC) init: untracked pid 2054 exited
  9. My pcDuino has been working well. Suddenly, it won't boot. Last message I see is: mounted filesystem with ordered data mode Whenever I put something in pcDuino (like mouse or keyboard) I see the response, but it still won't boot. Any help? P.S. Here is the screenshot.
  10. FIRST 2973

    update and upgrade issues

    I updated, upgraded and turned on wifi on my PCDuino3. Now the PCDuino3 does not finish booting up on my screen. I get the following error: ply_terminal_set_mode 630 assertion terminal and my screen goes blank. I am able to ssh into the PCDuino3 using a wired Ethernet. Do you have any suggestions? I have another PCDuino3 an it works fine but I did not installed the update/upgrade. I tried to re-image the kernel but all attempts failed using PheonixSuite. I read that I might need a special microSD card. Has anyone installed an update and upgrade on the PCDuino3?
  11. Klaafstra99

    Booting from SATA

    Hi there, After some fiddling and googling I am stuck. I cannot get my pcduino to boot from the harddisk. I tried the approach from this link but after changing the uEnv.txt on my sdcard (to /dev/sda1) I am stuck. Then I can only boot from nand. Is there anyone out there who can please post the steps necessary to change the rootfs to a SATA drive? Regards.
×