No Activity

bradsilcox
 
Posts: 1
Joined: Wed Dec 03, 2014 7:51 am

No Activity

Wed Dec 03, 2014 7:57 am

When I received my VoCore I powered it up, connected from my tablet and took a quick look. I had set it aside on my desk at work until I had located the stl files and was able to print a case. Now that I have a case I am not able to see the VoCore anymore. I've removed it from the case and see that when power is applied the LEDs light up but no activity is seen after that (I know when I first powered it up the LEDs had quite a bit of activity). I have not had a chance to connected via the TTL adapter as it does not appear to be detected on my system (no activity on the T, R, P leds on that board either). Can anyone tell me what I did wrong or if I can recover this device?

harrisonhjones
 
Posts: 5
Joined: Tue Dec 02, 2014 9:50 pm

Re: No Activity

Fri Dec 05, 2014 3:43 am

Without having a look using the TTL adapter it's going to be hard for anyone to help you (I imagine). How about you get that working and open a serial terminal to the TTL adapter before powering up the VoCore so we can get a look at the bootup sequence?

kbowley
 
Posts: 6
Joined: Fri Dec 05, 2014 8:07 pm

Re: No Activity

Fri Dec 05, 2014 8:21 pm

I have a similar problem. My VoCore was working fine, even sshed into it and looked around. I brought it to work when I printed out the shell, and everything was still working. when I attempted to connect it to the network with the ethernet cable, it stopped working. I attempted to connect with the USB2TTL adapter, but I don't see any activity. The lights come on when I connect power, but that's it.

kbowley
 
Posts: 6
Joined: Fri Dec 05, 2014 8:07 pm

Re: No Activity

Sat Dec 06, 2014 5:01 pm

I managed to get a serial console and see uboot. Looks like the image got corrupted. I used kermit to load a new image (loadb, send file, erase linux, cp.linux, power cycle). Now the lights come on, and nothing from uboot. Any ideas on what to do next?

Vonger
 
Posts: 896
Joined: Sun Oct 19, 2014 6:00 am

Re: No Activity

Sun Dec 07, 2014 3:50 pm

USB2TTL request a driver, it is PL2302/PL2303 driver. Please download it at its official site: http://www.prolific.com.tw/US/ShowProdu ... -0037-0041

kbowley
 
Posts: 6
Joined: Fri Dec 05, 2014 8:07 pm

Re: No Activity

Sun Dec 07, 2014 4:34 pm

Something seems to be wrong, but not sure what at this point. It attempted to boot again, but I didn't hit 'x' in time. This is what it showed:
Code: Select all
U-Boot for VoCore(based on RT5350)Warning: un-recognized chip ID, please update bootloader!
raspi_wait_ready: read_sr fail: ff

Version: May 30 2014 20:52:36

Press 'x' to console...


Booting image at bc050000 raspi_wait_ready: read_sr fail: ff
Bad Magic Number,00000000

Vonger
 
Posts: 896
Joined: Sun Oct 19, 2014 6:00 am

Re: No Activity

Sun Dec 07, 2014 5:19 pm

Looks like the firmware is broken, you have to use uboot to recover it.
Please check vocore.io/wiki. There is tutorial about how to fix firmware through USB2TTL.

kbowley
 
Posts: 6
Joined: Fri Dec 05, 2014 8:07 pm

Re: No Activity

Sun Dec 07, 2014 5:34 pm

I will attempt to repair the firmware if I can get uboot to start up again. Most of the time the only thing that happens when I apply power is the lights come on, but no activity from uboot on uart.

Good news: I finally got uboot to start and appear to have successfully updated the firmware.
Code: Select all
VoCore> cp.linux 300004
current count: 3145732

 Copy linux image[3145732 byte] to SPI Flash[0x00050000]....
raspi_write: to:50000 len:300004
.................................................


Bad news: uboot only seems to boot on vary rare occasions. When it does start, uboot seems to work normally. I've tried using the USB port on the laptop, and using a dedicated wall charger. Hopefully I'll be able to get this to boot again to see if the firmware works.

kbowley
 
Posts: 6
Joined: Fri Dec 05, 2014 8:07 pm

Re: No Activity

Mon Dec 08, 2014 2:04 pm

I think my VoCore has some serious problems.

## Total Size = 0x00300004 = 3145732 Bytes
## Start Addr = 0x80100000
VoCore> cp.linux 300004
current count: 3145732

Copy linux image[3145732 byte] to SPI Flash[0x00050000]....
raspi_write: to:50000 len:300004
...raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff
raspi_wait_ready: read_sr fail: ff

Peter H
 
Posts: 58
Joined: Wed Nov 12, 2014 10:24 pm

Re: No Activity

Mon Dec 08, 2014 3:15 pm

Which image are you trying to flash? If it's one you built yourself, you could try flashing the current VoCore OpenWrt image first to see whether it's a fundamental problem, or just an issue with your image.

Next
Return to VoCore & VoCore+Dock

Who is online

Users browsing this forum: Google [Bot] and 20 guests