I hear this sadly, I hope your other devices have not suffered harm.
Posts by dtech
-
-
I looked at the pictures taken from the PCB:
This version has 4 x 256MB of memory, which is relatively rare solution. (The 2 x 512MB solution is the most common.)
Most likely this is why most bootloaders are not good for this specific model.
We should look for stock ROMs that have the same 4 x 256MB layout.
-
The functionality of the MAX232 IC can be tested by connecting the RX and TX pins together and typing a character into the terminal.
If the typed character does not appear or only noise is displayed, then the reasons may be as follows:
- the power line is broken: Vcc is missing or GND is floating (broken wire),
- the voltage is unstable or lower than +5V,
- the Maxim IC is faulty.
If the MAX232 receives Vcc voltage (+5V) and the GND pins are also connected between the power source (such as USB port) and the other devices (RS232 pin 5 and the GND on the UART port of the box), the converter power should be OK.
If the bootloader has been overwritten (or just erased its area), I have a strong suspicion that we will not get anything through UART.
But I have never met one like this before, so I don't know for sure. I think chewitt has more experience with this.
At what percentage does the USB Burning Tool stop?
Quote from 'Amlogic Platform USB Burning Tool V2 User Guide - Revision 1.0.pdf'Display MoreProgress bar percentage:
- 0~2%:
During this stage:
1) If erase_bootloader is selected, then erase Bootloader and reboot.
2) Initialize burning environment and get the icon resources etc., from burning package.
! If burning fails and stay at 2%. It means flash initialization fails! - 2%~5%:
This stage is for flash initialization. If erase_flash is selected, it will also erase flash. - 6%~94%:
This stage is for burning the data partitions except for Bootloader. If the progress bar stops here, it means partition burning fails. - 96%~98%:
This stage is for burning bootloader. - 100%:
Burn successfully.
-
Maybe not, but where does the MAX232 get its Vcc (5V) voltage?
-
That seems like noise. What baud rate did you set? 115200?
Do you use MAX232 to connect to the TTL port?
Please calm me down, that you did not solder the serial port RxD and TxD pins directly to the device.
-
Still hoping to see the WeTek core get 9.2 or 10 one day...
Actually, I also created an image for WeTek Core on request, but the user for whom it was made has not logged in to the forum since April.
So you would do me a favor if you could test it, because this is the only image I didn’t get feedback on whether it works okay or not.
LibreELEC v9.2.8 image for WeTek Core:
-
LibreELEC v9.2.8 has been released for some Amlogic S805/S8X2/S905 devices and WeTek Play.
Changes:- glibc: Apply an updated widevine fix for v4.10.2252.0 or newer version,
- cputemp: Fix millidegree issue, if the kernel return value is specified in it,
- projects/WeTek_Play: Add support WP1 and re-enable CPU temperature sensor in the kernel,
- projects/S8X2: Add an option to override power off in Kodi (workaround for the uboot power bug).
For more information and for download links, please check the first post in this topic: #1
-
Well, it's still a little hard to read, but I managed to recognize it.
This is a 2GB LPDDR3 memory chip from Samsung. It was important information.
Okay, the next step will be when the TTL adapter arrives...
-
Okay, so far only three people do not understand sarcasm.
-
i understood nothing
I think your description has become a little too detailed.
Could you clean the top of the memory chip with something? (Like isopropyl alcohol or brake cleaner.)
And then you should take a good quality macro photo of the caption on it.
This is the memory chip on your PCB:
(For better readability, use the flash, but do not place the camera perpendicular to the PCB.)
-
9.2.8 is already build and is intern tested, due summer/holidays etc we are slower then usual
Ok, I accept this answer "partially".
But regardless, I hope I don’t have to ask again in two weeks.
-
yes I do a release, soonish
basically just waiting a bit if some additional changes are needed
Another two weeks passed... Will version 9.2.8 ever be released at all?
It looks like a stable version of LE 10 will be released sooner than a bug-fixed version of LE 9.2.
I understand that the old version no longer gets priority, but there is still a buggy v9.2.7.
It has been released for a month and a half, and I don't understand the reason for this long wait when the fix is already available.
-
In fact, any of these can be good, it's not an expensive thing.
-
Without a soldering iron and a TTL converter, you cannot determine what is causing the error.
Unfortunately, the description is not enough for this now, it also requires some physical tools.
-
Do you have an USB-TTL adapter (or an RS232-TLL converter)?
Somehow you should see what happens when you start the device.
-
In the meantime, we managed to unbrick the KI Plus S905D (1G/8G) in the background with creited.
The vendor never released a factory image (only an OTA update was released), so it was impossible to repair the bricked devices so far.
I was able to create an image, close to the factory ROM state, that could be used with the USB burning tool:
-
please suggest flashing method also, to use...
Of course, you need to use USB burning tool and a USB A-A cable.
The contacts do not need to be shorted, just press and hold the button on the bottom of the PCB when connecting the USB cable.
-
Stock ROM for KII Pro devices based on S905D SoC:
