[stane1983]

Hi guys,

Based on Pivos sources, I made ATV-102 (Amlogic f16ref board) linux xbmc build. It's still WIP but works

Link: https://www.dropbox.com/s/5f17g968k9njtx...-05-12.zip

Released as complete firmware update package. Uboot will be changed when flashing (if u-boot-aml-ucl.bin is not removed from sdcard), so be carefull.

Do not flash on 512MB devices!

Regards,
Stane1983

[antonymathew]

hi stane.. thanks a lot for the XBMC built...

should i follow the same method of resetting the device on power on with all these files in SD card to perform this update.
I have once wrongly made an update (not with this xbmc built) and device is halted with blue and red LED always on.
Is my device non-recoverable now ?
please help....

mine is the 1GB device from Visson (ATV-102 - f16ref board)

Regards
Antony mathew

[stane1983]

hi stane.. thanks a lot for the XBMC built...

should i follow the same method of resetting the device on power on with all these files in SD card to perform this update.
I have once wrongly made an update (not with this xbmc built) and device is halted with blue and red LED always on.
Is my device non-recoverable now ?
please help....

mine is the 1GB device from Visson (ATV-102 - f16ref board)

Regards
Antony mathew

Hi,

see these 2 threads:

http://androidforums.com/stanes-roms/614...logic.html

http://androidforums.com/stanes-roms/691...igger.html

Second thread describes how to trigger booting from recovery sdcard on Visson f16ref (if it doesn't work with normal power-on with reset pressed).

I deleted XBMC fw from dropbox, most probably won't work with my u-boot-aml-ucl.bin on devices that have stock firmware (will switch to 576i resolution). If you have stock uboot, use that instead.

[antonymathew]

hi stane.. thanks for the info.. i will do it soon and update....

anyway sorry for being more specific......

is the pins u mentioned to short are the Chip select (CS#) and SO/SIO on the SPI chip.

thanks again

[antonymathew]

hi stane that was a big help.. i tried the recovery SD card method (not the SPI pin shorting method) with the uboot file in your XBMC build for board (since i dont have the original uboot)..

below is the tool i used to copy uboot and other files to SD card

the tools works under Windows XP only (Virtual Xp mode in my Win7 PC didnt help)
http://www.mediafire.com/?u4oegdnaalpky2m

The method after creating the bootable SD card was
1. Inserted SD card. Kept device Off and reset button pressed.
2. Powered the device with reset pressed still. Blue and RED leds glows
3. waited untill Blue LED starts blinking. Release the Reset.
4. Within 2 minutes XBMC loading logo appeared . It is shifted in view. only a part is visiblle on TV
5. Waited on that screen for 30 minutes. Blue LED blinks at steady rate... No progress...

the screenshot is
http://tinypic.com/view.php?pic=2hhgi0i&s=5


Can u help me with an Uboot file which is perfect for the device.. i will try it out with XBMC built.

Thanks again for resurrecting my device

regards
Antony

[stane1983]

hi stane that was a big help.. i tried the recovery SD card method (not the SPI pin shorting method) with the uboot file in your XBMC build for board (since i dont have the original uboot)..

below is the tool i used to copy uboot and other files to SD card

the tools works under Windows XP only (Virtual Xp mode in my Win7 PC didnt help)
http://www.mediafire.com/?u4oegdnaalpky2m

The method after creating the bootable SD card was
1. Inserted SD card. Kept device Off and reset button pressed.
2. Powered the device with reset pressed still. Blue and RED leds glows
3. waited untill Blue LED starts blinking. Release the Reset.
4. Within 2 minutes XBMC loading logo appeared . It is shifted in view. only a part is visiblle on TV
5. Waited on that screen for 30 minutes. Blue LED blinks at steady rate... No progress...

the screenshot is
http://tinypic.com/view.php?pic=2hhgi0i&s=5


Can u help me with an Uboot file which is perfect for the device.. i will try it out with XBMC built.

Thanks again for resurrecting my device

regards
Antony

This uboot is just fine except I made misstake and didn't build a new one for xbmc. Ubootenv variables were reset because of different ubootenv offset location on SPI. Problem you're facing is that default outputmode (screen resolution) is set to 576i (complicated, don't ask ). If you have UART console you can connect to, quickest solution would be just interrupting boot and setting outputmode value to 720p like this:

Code:

setenv 'outputmode' '720p'
saveenv
reset

Thats the reason why I deleted file from dropbox.... I'm busy with other things atm so did not manage to rebild m3 uboot yet. Sorry for inconviniences.

[antonymathew]

oops... i dont have a uart console.. but will find one soon.. but what is much complex is to find the UART pins on board.. can u give me some light on that... Is it the unpopulated j2 header..

[stane1983]

oops... i dont have a uart console.. but will find one soon.. but what is much complex is to find the UART pins on board.. can u give me some light on that... Is it the unpopulated j2 header..

Yes, j2 header is TTL v3.3.

Pinout if leds are facing you:

- 3.3v (don't have to solder)
- TX (goes to RX on adapter)
- RX (goes to TX on adapter)
- GND (little tricky to solder, use higher temp)

[DroidTV]

hi stane.. thanks a lot for the XBMC built...

should i follow the same method of resetting the device on power on with all these files in SD card to perform this update.
I have once wrongly made an update (not with this xbmc built) and device is halted with blue and red LED always on.
Is my device non-recoverable now ?
please help....

mine is the 1GB device from Visson (ATV-102 - f16ref board)

Regards
Antony mathew

Hi,

see these 2 threads:

http://androidforums.com/stanes-roms/614...logic.html

http://androidforums.com/stanes-roms/691...igger.html

Second thread describes how to trigger booting from recovery sdcard on Visson f16ref (if it doesn't work with normal power-on with reset pressed).

I deleted XBMC fw from dropbox, most probably won't work with my u-boot-aml-ucl.bin on devices that have stock firmware (will switch to 576i resolution). If you have stock uboot, use that instead.

I'm getting the:
"This site is closed at the moment." message when I try to download app for Amlogic Recover SD card creation ((
Could you please update the link?
Thank you very much!

[stane1983]

hi stane.. thanks a lot for the XBMC built...

should i follow the same method of resetting the device on power on with all these files in SD card to perform this update.
I have once wrongly made an update (not with this xbmc built) and device is halted with blue and red LED always on.
Is my device non-recoverable now ?
please help....

mine is the 1GB device from Visson (ATV-102 - f16ref board)

Regards
Antony mathew

Hi,

see these 2 threads:

http://androidforums.com/stanes-roms/614...logic.html

http://androidforums.com/stanes-roms/691...igger.html

Second thread describes how to trigger booting from recovery sdcard on Visson f16ref (if it doesn't work with normal power-on with reset pressed).

I deleted XBMC fw from dropbox, most probably won't work with my u-boot-aml-ucl.bin on devices that have stock firmware (will switch to 576i resolution). If you have stock uboot, use that instead.

I'm getting the:
"This site is closed at the moment." message when I try to download app for Amlogic Recover SD card creation ((
Could you please update the link?
Thank you very much!

Here you go: SDTool.zip

[antonymathew]

oops... i dont have a uart console.. but will find one soon.. but what is much complex is to find the UART pins on board.. can u give me some light on that... Is it the unpopulated j2 header..

Yes, j2 header is TTL v3.3.

Pinout if leds are facing you:

- 3.3v (don't have to solder)
- TX (goes to RX on adapter)
- RX (goes to TX on adapter)
- GND (little tricky to solder, use higher temp)

wow... that was quite an info..thanks a lot.... going to order an USB-UART debugger . thanks a lot...

[DroidTV]

Thank you very much. Unfortunately I can't download the Linux Build file from drop box. I get - "Nothing Here
The file you're looking for has been deleted or moved."

[jevgenijo]

Stane1983, I sent your thread to the Visson representative and they are going to try it on the ATV-102 very soon. :-D Now I have to try to recover bricked ATV-102 I do have. ))
I see you have spend much time porting the Pivos build into the ATV-102. Soon we are going to start portion of the Linux Build for XBMC into the 8726MX box. Would you like to participate into that:
Please visit this thread if you will be interested - http://forum.androidgadget.co.uk/showthread.php?tid=148

[stane1983]

Stane1983, I sent your thread to the Visson representative and they are going to try it on the ATV-102 very soon. :-D Now I have to try to recover bricked ATV-102 I do have. ))
I see you have spend much time porting the Pivos build into the ATV-102. Soon we are going to start portion of the Linux Build for XBMC into the 8726MX box. Would you like to participate into that:
Please visit this thread if you will be interested - http://forum.androidgadget.co.uk/showthread.php?tid=148

Hi

I'm actually cooperating with Visson and they are very familiar with all my work regarding their M1, M3 and MX devices, but thanx for your effort

About MX, I have XBMC Linux up and running on Visson board (ATV-103 aka Tronsmart Prometheus; Tronsmart have exclusive for their spaceship box design in China) with few bugs to solve. I saw thread on Peters forum, will reply to your PM.

Regards

[jevgenijo]

Wow, good job! Would love to test your release for Prometheus
I was pretty sure that the model number for Prometheus was ATV-106, not the ATV-103