Ubuntu Utopic for nvidia shield tv

[Thanks_Meter]

u-boot would be really great. Maybe anybody can find out, if there are the UART pins available on the mainboard. I've just opened my Shield months ago, but wasn't able to see any UART pins. But I guess, it could be there - one have to dismount the mainboard, maybe the UART pins are hidden below...:fingers-crossed:

Maybe there is a way to use an USB to serial converter for this if there is something like CONFIG_USB_SERIAL_CONSOLE in the uboot config.

 

[crnkoj]

u-boot would be really great. Maybe anybody can find out, if there are the UART pins available on the mainboard. I've just opened my Shield months ago, but wasn't able to see any UART pins. But I guess, it could be there - one have to dismount the mainboard, maybe the UART pins are hidden below...:fingers-crossed:

I agree. I have thought of putting u-boot in Boot partition and put kernel/rootfs/dtb on SD or USB drive.

I have built u-boot's for Jetson TK1 and TX1 and tested on TK1. The problem is none has figured out how to add serial console port for SATV (Shield Android TV) and it's difficult to test u-boot without console logs.

I have read netconsole and OTG console for some ARM processors, but u-boot's for Jetson TK1 and TX do not have netconsole or OTG console implemented.

I do honestly not believe that UART is there or if its there, that its functioning.
How did oy umanage to build the u-boot? do you have any tutorial? did you just download teh srouces for uboot from l4t and than compile it? probably we need to use other dtb from the kernel for the shield in there and possibly some other changes (like EMMC/UMS). might have to try blindly to boot it...

 

[yahoo2016]

I do honestly not believe that UART is there or if its there, that its functioning.
How did oy umanage to build the u-boot? do you have any tutorial? did you just download teh srouces for uboot from l4t and than compile it? probably we need to use other dtb from the kernel for the shield in there and possibly some other changes (like EMMC/UMS). might have to try blindly to boot it...

I used "source_sync.sh" in L4T for TK1 and TX1 to download u-boot source code and built u-boot images, see posts there:

https://devtalk.nvidia.com/default/topic/905345/built-tx1-u-boot-from-source/

I suspect u-boot has dtb built-in for itself. The dtb in dtb partition is for kernel.

 

[Thanks_Meter]

I suspect u-boot has dtb built-in for itself. The dtb in dtb partition is for kernel.

As far as I know u-boot does not use dtbs for its own. For this reason you must do things like setting up the pinmux or configurating the drivers manually in c-code (like linux kernel prior to 3.8).

 

[yahoo2016]

As far as I know u-boot does not use dtbs for its own. For this reason you must do things like setting up the pinmux or configurating the drivers manually in c-code (like linux kernel prior to 3.8).

My point was bootloaders (u-boot or fastboot) do not need the dtb in dtb partition (which is for kernel only) to function, replacing dtb in dtb partition should not cause bootloaders or recovery mode to fail.

Some members bricked their SATV by replacing dtbs, I don't believe it's dtb issue, but issue of post V1.3 bootloader. When wrong dtb was put in dtb partition, kernel failed to load, but recovery mode should still work.

That's why I recommend to revert to ROM 1.3 which has more reliable recovery mode.

 

[kgersen]

some guys managed to get a full Linux 4 Tegra 64 bit to run on the Shield: http://blog.hypriot.com/post/gettin...ighend-arm-gaming-console-for-fun-and-profit/

no X11 yet and so far they haven't published their changes but they will.

It's a promising start, something to watch and if you can help them , they're asking for it:

Maybe there are some of you who - after reading this article - want to get started hacking on the ShieldTV, too. We really would appreciate getting some help here to move faster. That’s why we will publish the technical details in the coming weeks, so you can have a look and start hacking yourself.

 

[tbm13]

some guys managed to get a full Linux 4 Tegra 64 bit to run on the Shield: http://blog.hypriot.com/post/gettin...ighend-arm-gaming-console-for-fun-and-profit/

no X11 yet and so far they haven't published their changes but they will.

It's a promising start, something to watch and if you can help them , they're asking for it:

This blog is written by dieter.reuter who has participated in this thread.

 

[praveenonwww]

Have any body tried Flashing Ubuntu with the step provided in the first of this thread for NVIDIA SHIELD ANDROID TV Pro Developer Only OS Image 3.0.0 from https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20ANDROID%20TV%20Pro%20Developer&tx=$additional,shield.

 

[gffmac]

Can the sdcard image be written to a usb external drive instead and boot from that?

 

[yahoo2016]

Can the sdcard image be written to a usb external drive instead and boot from that?

you''ll need to change "init.c" to boot from /dev/sda1 (first partition of USB drive) instead of /dev/mmcblk1p1, see here:

http://forum.xda-developers.com/showpost.php?p=65401522&postcount=187

If you updated to SATV SW 3.0, you won't be able to boot to ubuntu using the kernel from this thread.

 

[gffmac]

you''ll need to change "init.c" to boot from /dev/sda1 (first partition of USB drive) instead of /dev/mmcblk1p1, see here:

http://forum.xda-developers.com/showpost.php?p=65401522&postcount=187

If you updated to SATV SW 3.0, you won't be able to boot to ubuntu using the kernel from this thread and the other thread.

Thanks, I will wait for a 3.0 based kernel to attempt this.

 

[mateusdsrs]

I have trouble to boot Ubuntu, after insert de SD card with linux image and boot nvidia_linux.img the shield restart and show nvidia start screen after this displays a black screen, after some moments with black screen restart it from zero .

tricks tempted

*change SD card
* flash de nvidia_boot on recovery shield partition
*download images the kernel e OS again

Thanks

 

[mateusdsrs]

I have trouble to boot Ubuntu, after insert de SD card with linux image and boot nvidia_linux.img the shield restart and show nvidia start screen after this displays a black screen, after some moments with black screen restart it from zero .

tricks tempted

*change SD card
* flash de nvidia_boot on recovery shield partition
*download images the kernel e OS again

Thanks

I think founded the problem, it´s the version of system of nvidia shield tv is 3.1, i can´t boot nome linux with any kernel image.
i go to back the system for 2.1 to can boot ubuntu.

 

[BlInK311]

I think founded the problem, it´s the version of system of nvidia shield tv is 3.1, i can´t boot nome linux with any kernel image.
i go to back the system for 2.1 to can boot ubuntu.

I am having the same issues where I cant boot into Ubuntu. My nvidia shield tv does have SW version 3.1 and I tested 3.0 that nvidia has an image for on their dev site. That didn't work either. Is there a prebuild image of 2.1 available? Or did you build it from sources?

 

[KzRSylveR]

I have the same issue, black screen after booting on nvidia_boot.img with nvidia-shield-tv-utopic.arm64.img.2G image on the SDCard... I'm seeking the 2.1 image to downgrade and try to boot on linux, but I don't find this image...

 

[mateusdsrs]

I have the same issue, black screen after booting on nvidia_boot.img with nvidia-shield-tv-utopic.arm64.img.2G image on the SDCard... I'm seeking the 2.1 image to downgrade and try to boot on linux, but I don't find this image...

BlInK311 and KzRSylveR I solved the problem of black screen after changing some system components will list exactly what I'm using . I believe that the upgrade 3.0 / 3.1 has a version of the previous boot obsolete.


*Write the SD Card with de Image the Ubuntu System ( I have used Ubuntu Xenial Image )
*Insert the sdcard In Shield TV
*Enable Dev options on Android tv
*install the adb/fastboot
*Reboot to bootloader with commands | adb devices and adb reboot bootloader
* Unlock the boot loader with fastboot oem unlock
*Download this kernel image from this link https://drive.google.com/file/d/0Bz5kaPQJx_AgcUJ2TlBTUW9ZR0k/view
* Boot the kernel with with this command fastboot boot boot.img

 

[KzRSylveR]

BlInK311 and KzRSylveR I solved the problem of black screen after changing some system components will list exactly what I'm using . I believe that the upgrade 3.0 / 3.1 has a version of the previous boot obsolete.
*Write the SD Card with de Image the Ubuntu System ( I have used Ubuntu Xenial Image )
*Insert the sdcard In Shield TV
*Enable Dev options on Android tv
*install the adb/fastboot
*Reboot to bootloader with commands | adb devices and adb reboot bootloader
* Unlock the boot loader with fastboot oem unlock
*Download this kernel image from this link
* Boot the kernel with with this command fastboot boot boot.img

Thanks for your reply, could you tell me where you dl this Ubuntu Xenial Image ?

Edit : I have trying with your boot.img, the screen stop to the nvidia logo, so no black screen, but after a long time Android booting instead of my SDCard with linux on it

 

[mateusdsrs]

Thanks for your reply, could you tell me where you dl this Ubuntu Xenial Image ?

Edit : I have trying with your boot.img, the screen stop to the nvidia logo, so no black screen, but after a long time Android booting instead of my SDCard with linux on it

Sometimes the Ubuntu boot does not work on the first try , try at least twice , I lost a lot of time to figure it out.

Link of Ubuntu Xenial https://drive.google.com/open?id=0B...ZSS1VxUVBJZmFqSXNFYUhpN2lHcklhVzZtX0Z5OENxdU0

Note: do not know why but Ubuntu Utopic in my case does not recognize the wired network card and a wireless network card.
The Xenial despite not having video driver, but works well stable

 

[heebe]

My problem is that Utopic, Xenial and Hypriot images boot great but they run stable only for 2-5 minutes. Then suddenly the whole device reboots and falls back into Android. I have experimented with these three images using two sd cards. All combinations show this rebooting behaviour. I have found no trails or hints in log files.

Has anyone else seen similar issues? Original android seems to work stableI have no trails or hints in log files.

 

[frankjt]

A note to the enforced rebooting of 3.0 / 3.1 systems, a possible cause is,
in addition to the kernel config, the device tree configuration of the tegra watchdog timer. Since version 3.0 the timer´s heartbeat is set to 120 seconds.
Within this time interval the system software, e.g. systemd, has to send at least
one ping to the watchdog device, otherwise the system reboots after a hardware
reset. In order to avoid that with systemd, in /etc/systemd/system.conf the option RuntimeWatchdogSec must be set to a non-zero value, e.g. 40s :
RuntimeWatchdogSec=40
(See man page of systemd-system.conf)
systemd will now send a ping to the hardware every 20 seconds.