For good measure, I should have posted those command outputs using
HK's old u-boot as well for comparison:
*
Exynos4412 # md.l 0x1000 0x1
1000: e4412220 "A.
*Same
Exynos4412 # md.l 0x1180 0x1
1180: 0222""".
*vs 0022
Exynos4412 # md.l 0x1188 0x1
1188: 00
On Wed, Apr 29, 2015 at 4:15 AM, Przemyslaw Marczak
wrote:
>
> Yes, it's good, that you mention that. The odroid_defconfig was tested only
> on U3 and X2. You can found the info here: doc/README.odroid.
"tested only on...", that I knew, but also knew the U2 and U3 both
used 4412 Prime and only had
Hello Nathan,
On 04/28/2015 10:49 PM, Nathan wrote:
On Tue, Apr 28, 2015 at 3:07 AM, Przemyslaw Marczak
wrote:
Sorry, I didn't reply last time, becouse I'm quite busy.
No worries. I was really just keeping you apprised of my findings.
If I good remember, Exynos 54xx doesn't support sdhci,
Hello Nathan,
Sorry, I didn't reply last time, becouse I'm quite busy.
On 04/28/2015 07:39 AM, Nathan wrote:
Still not sure where the problem lies. I thought I found an issue, but
it didn't fix anything and caused a different issue.
At first, after plugging in a bunch of printfs, I thought it
Still not sure where the problem lies. I thought I found an issue, but
it didn't fix anything and caused a different issue.
At first, after plugging in a bunch of printfs, I thought it was a
simple issue in the dts (it appears not to be the issue):
*
Getting a little back into it, I find an is
I had tried another card with the same result. I didn't think it would
be a problem since the hardkernel's release still works.
I expanded the output by defining "DEBUG" and am updating my thread
with my new findings:
...
Bound device i2c@138d to root_driver
- ignoring disabled device
Hi,
On 03/10/2015 02:14 PM, Nathan wrote:
Sure, I understand from seeing all of the patches you submit. I
thought I'd at least ask in case it was something easy.
I'll continue to look into it. Thanks for submitting those links.
>
I didn't try any other sdcard since the card does work fine wit
Sure, I understand from seeing all of the patches you submit. I
thought I'd at least ask in case it was something easy.
I'll continue to look into it. Thanks for submitting those links.
I didn't try any other sdcard since the card does work fine with
Hardkernel's old pre-built binaries.
On Tue, M
Hello Nathan,
On 03/10/2015 12:30 PM, Nathan wrote:
I hope my last message didn't get lost during that outage last month.
In the mean time, I had to finagle the HardKernel code to work with
GCC 5.0 which ended up being only 1 line change which I may end up
encountering in mainline if I ever get
I hope my last message didn't get lost during that outage last month.
In the mean time, I had to finagle the HardKernel code to work with
GCC 5.0 which ended up being only 1 line change which I may end up
encountering in mainline if I ever get far enough.
After transferring the "CONFIG_MMC_TRACE"
On Fri, Feb 27, 2015 at 7:16 AM, Przemyslaw Marczak
wrote:
> This is too late for debug. The same result I can see when my card is not
> inserted.
Ugh, I meant to include the link to my post in the odroid forums which
included the entire (very long) output:
http://forum.odroid.com/viewtopic.php?f=
Hi,
On 02/27/2015 12:59 AM, Nathan wrote:
I think I've been able to narrow down, a bit, where the issue is coming from.
"mmc_set_blocklen" led me to "mmc_send_cmd" which showed that there is
the "CONFIG_MMC_TRACE" I could use.
A notable difference between hardkernel's u-boot and mainline was t
Hello Nathan,
On 02/26/2015 01:30 AM, Nathan wrote:
Wow, that came out as a real mess.
I used Outlook.com to compose that message.
Anyone experience that and can recommend how I can clean it up?
I see that I composed using "Rich Text".
I'll try to redo it in my reply here using "Plain Text":
I think I've been able to narrow down, a bit, where the issue is coming from.
"mmc_set_blocklen" led me to "mmc_send_cmd" which showed that there is
the "CONFIG_MMC_TRACE" I could use.
A notable difference between hardkernel's u-boot and mainline was the
"uint flags;" was no longer in the "mmc_cm
Wow, that came out as a real mess.
I used Outlook.com to compose that message.
Anyone experience that and can recommend how I can clean it up?
I see that I composed using "Rich Text".
I'll try to redo it in my reply here using "Plain Text":
"saveenv" won't write the environment out to disk.
$ su
"saveenv" won't write the environment out to disk.
$ sudo dd if=/dev/zero of=/dev/sde seek=1 bs=512 count=3999 //wiping out area
just to make sure no garbage is picked up.$ sudo dd if=bl1.HardKernel
of=/dev/sde seek=1 iflag=dsync oflag=dsync$ sudo dd if=bl2.HardKernel
of=/dev/sde seek=31 iflag=
16 matches
Mail list logo
