On Tue, Jan 28, 2020 at 11:40 AM JH wrote:
> Hi Gabriele,
>
> On 1/28/20, Gabriele Zampieri wrote:
> > HI JH,
> >
> > - Can you stop on uboot and try "nand bad"? This will list the bad blocks
> > on your device.
> => nand bad
>
> Device 0 bad blocks:
>
>
> > - How do you flash your ubi
Hi Gabriele,
On 1/28/20, Gabriele Zampieri wrote:
> HI JH,
>
> - Can you stop on uboot and try "nand bad"? This will list the bad blocks
> on your device.
=> nand bad
Device 0 bad blocks:
> - How do you flash your ubi partition(s)?
I boot zImage-initramfs kernel to Linux user space, then
HI JH,
- Can you stop on uboot and try "nand bad"? This will list the bad blocks
on your device.
- How do you flash your ubi partition(s)?
- During boot, does ubifs layer complain about the partition is it trying
to mount? It will in case of corrupted metadata and may result in a read
only mount.
On 1/27/20, Quentin Schulz wrote:
> Hi JH,
>
> On Mon, Jan 27, 2020 at 10:13:37PM +1100, JH wrote:
>> Hi Andy,
>>
>> Thanks for the response.
>>
>> On 1/27/20, Andy Pont wrote:
>> > JH wrote...
>> >
>> >>That the same problem of missing busybox was not just occurred during
>> >>the device
On 1/27/20, Jonatan Palsson wrote:
> Hello JH,
>
> On Mon, Jan 27, 2020 at 12:13 PM JH wrote:
>>
>> > If you look at the /bin directory (ls -la /bin/busy*) what do you see?
>> > Have the files been deleted? Truncated? Zero length?
>>
>> Could not run ls or any shell commands when the busybox was
Hi Laurent,
On 1/28/20, Laurent Gauthier wrote:
> Hi JH,
>
> As you are not providing enough details in your request we have to
> guess the nature of
> the issue you are seeing.
Let me know what kind of details I haven't provided.
> I will just point out a few things that could help in your
Hi JH,
As you are not providing enough details in your request we have to
guess the nature of
the issue you are seeing.
I will just point out a few things that could help in your situation.
If this is a failure that happens almost every time after you flash a
new image it could be
due to NAND
Hi JH,
On Mon, Jan 27, 2020 at 10:13:37PM +1100, JH wrote:
> Hi Andy,
>
> Thanks for the response.
>
> On 1/27/20, Andy Pont wrote:
> > JH wrote...
> >
> >>That the same problem of missing busybox was not just occurred during
> >>the device running in the middle of operation, it was also
Hello JH,
On Mon, Jan 27, 2020 at 12:13 PM JH wrote:
>
> > If you look at the /bin directory (ls -la /bin/busy*) what do you see?
> > Have the files been deleted? Truncated? Zero length?
>
> Could not run ls or any shell commands when the busybox was missing.
Do you have the "ubifsls" command
Hi Andy,
Thanks for the response.
On 1/27/20, Andy Pont wrote:
> JH wrote...
>
>>That the same problem of missing busybox was not just occurred during
>>the device running in the middle of operation, it was also occurred
>>during booting image from NAND, I saw several times that the first and
JH wrote...
That the same problem of missing busybox was not just occurred during
the device running in the middle of operation, it was also occurred
during booting image from NAND, I saw several times that the first and
second cycles of booting image from NAND were working well, then some
Hi,
I have further investigated the problem, here is more information:
That the same problem of missing busybox was not just occurred during
the device running in the middle of operation, it was also occurred
during booting image from NAND, I saw several times that the first and
second cycles of
12 matches
Mail list logo