Balbes, In kodi 19 waipu tv is integrated as a pvr client. But not in your image. Of course, I don't know what's available to you. Thank you for your great work.
There are no binary Addons for KODI-19 yet. Use versions with KOD-18
Posts by balbes150
-
-
-
store init 3
This command full erases all eMMC.
First, try in the UART console to run the command "defenv" and then the second command "saveenv". This will reset all variables to their original state. After that, you can try to write the regular firmware via USB Burn Tool.
After that, you can normally activate the multi-boot and run the LE from external media and install in eMMC without the risk of killing the TV box.
-
if I want to use sd and emmc at the same time now, there is then a selection menu which os or whether sd, emmc or usb can be booted?
In this SPIboot no Piteboot. Perhaps with the transition to u-boot-2019 for SPIboot, I will include support for choosing the startup system by regular means of u-boot itself (if I find free time for this).
In this version SPIboot, the choice of the system run automatically, the order in which the media. You can set the desired order of the poll (run). For example, if there is a USB drive with the system, start USB first, if there is no USB (disconnect the USB drive), start from eMMC (or SD).
can you add the waipu pvr addon from orig kodi19?
I don't understand your question. Describe in detail the essence of the problem.
The problem I have now is that I can't start the tvbox from the remote. Maybe he has modified the uboot. Is there any solution or do I have to put the android stock again to recover the boot with the remote?
What systems have you run before ?
result : continues restarts about 15 sec after logo show up.
Corelec previously ran on this hardware ?
i am trying with build odroid N2 but green screen and i dont know how to force rgb color or another solution.good work
-
I stumbled upon this thread on the search for a newer build of libreelec for the rockpro64. Unfortunalty your latest images doesn't boot at all the the RockPro64, even the LEDs doen't start. The latest armbian (nightly with 5.3) works great on my rockpro, but i am too lazy to try to get Kodi running on a nightly build.
It it just a problem in the DTB maybe you can try the armbian DTB file of the RockPro.
Sorry if I hijack the thread. I can always open a new one, but I don't know if your files should even be tested yet
1. Have you checked all DTB from the image LE ?
2. Have you checked the startup LE, if you copy the DTB from Armbian and use it ?
3. There can be several problems, u-boot is not suitable for your model, DTB is not suitable, kernel configuration is not suitable. To solve it, you need to determine exactly what prevents the launch.
p.s. Perhaps these questions need to discuss in appropriate topic Pro your model.
-
new image 20190922
kodi-18 and kodi-19
-
I would still have time for a test today, then again at the weekend.
I uploaded the new version of the LE (20190920) for RK3399. It added the DTB to T4. Please check if this image works with the new DTB.
-
The problem is, I don't know how to flash it all. So far I have flashed the image per balea etcher on a sd or emmc, and set the switch on the odroid N2 4gb to emmc. Power on, installation and done! Unfortunately, I do not know what other possibilities are available. Would like to learn it. And once I've got it, I can better give German support
You can use steps . Download and burn the LE image as usual to the SD card. Download and copy the file (spiboot.img) on the same medium where the LE is recorded. Disconnect eMMC (if it is connected to N2). Switch the load source switch to SPI mode (left position). Connect the media to N2 and turn on the power. The system should automatically start the SPI update. After the SPI update and automatic reboot, the LE should automatically start. After updating the SPI, you can use USB media to run the LE. I pay attention, for work of the new mode of start-up of all carriers (USB SD eMMC PXE), the switch has to remain in the SPI mode. Additional details how to update SPIboot and official versions of the firmware for it, see here.
-
So, I tested it with the DTB directly from the image.
I need info to compare how dtb works from the LE image and how LE will work with the new file (which I sent to you on the website). And the second comparison, the dtb LE from the image and the dtb file which you take from Recalbox. I need to understand which elements in the dtb from the LE image are different from the working dtb (what needs to be fixed in the dtb from the LE). By the way, on the EDGE Armbian 4k resolution and 4K video works, and therefore at T4 can try to find the cause of the problem.
-
No, or let's say once until about May I tried again and again to use the DTBs from your images.
But there was always no WiFi device detected.
Via dmesg I could see that.
A modprobe on bmdhd failed because no device was found.
I'm interested in the overall system startup. The rest can be corrected later.
-
Try running this image Armbian on T4. It includes DTB for nanopc-t4.
-
Is the DTB file rk3399-rockpro64.dtb the one from your last LE images at
No, it's a new file. Maybe in the next images I will add this new DTB for T4.
But you can check yourself, will work DTB rockpro64 from the image LE or not.
PS Alas, I have no T4 for tests, significantly reduces the speed of debugging.
-
Sorry, i have renamed this DTB file:
Ayayay ....
Try this dtb on T4. You can rename it for yourself as convenient
. I am interested to start LE and Armbian. -
I downloaded the image Recalbox on your link. It has only a single DTB file with name (rk3399-rockpro64.dtb). Where did you the file with name (rk3399-nanopc-t4.dtb) ?
-
The desktop works up to 1920x1024x60Hz.
Good
I just can't get WiFi to work right away. I have to look at the logs again and get back to you.
Perhaps for WiFi need add firmware, by default there minimal set of firmware.
it will be useful to check the installation of a media script that includes HW on Armbian and allows you to watch any video in full screen.
[Development] RK3399 media script - Rockchip 3399 - Armbian forum
-
Hi
What is exactly the file you are using (copying) from the image Recalbox ? I need the full name of the DTB file used. If running Armbian happens, you can try to perform the initial configuration. If you took a desktop image, you need to log in to the console as "root" with the password 1234, change the password, create a new user, set the password and see if the graphical desktop shell will start.
-
Thank you balbes, I took that spi and flashed it on sd card, but it doesn't happen
Write more about what and how you do it.
On my N2 all good starts and runs.
-
1. You can specify the name of the DTB file are you using from the image Recalbox ?
2. You can perform a simple test of image is running Armbian
https://yadi.sk/d/tpeis4lvlmgtvq
(I'm interested in two things, will it work booting u-boot on a T4 and what DTB from the image Armbian will have better hardware support T4) ?
