View Single Post
Old 06-08-2017, 11:58 PM   #43
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Now, post the output of:
printenv

Please try to keep in mind that you have a hardware model that has never been seen by anyone who has written prior posts.

I.E: You can't just presume that things like the memory map is the same on your PW3-32 and on the PW3-4.
That includes the memory locations of things like the 'diag' kernel.

= = = =

Please post the Japanese links to both the *.bin update package and the corresponding source code.
I (or somebody) needs to read the u-boot code for your model before you proceed any further.

We can not just assume that your mini-uboot build will run the same as the PW3-4 mini-uboot build!

- - - -

But if it does - -
You load the desired u-boot binary into RAM -
Execute it -
Then run 'Erase All' -
At the end of the erase the entire eMMC (and it does, just 'like new') that command will write a copy of the currently executing uboot (and the saved device specific data) to the erased eMMC.

Translate this:
DO NOT attempt the above steps until somebody has read the source code specific to your model to confirm that your build will behave the same.
knc1 is offline   Reply With Quote