On Wed, Apr 29, 2015 at 4:15 AM, Przemyslaw Marczak
p.marc...@samsung.com 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
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:
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
It is possible for CONFIG_XILINX_EMACLITE to be defined without
XILINX_EMACLITE_BASEADDR being defined as the EMAC Lite driver support
OF init. Check that the driver is enabled and the base address is
available before initializing with a static base address.
Signed-off-by: Nathan Rossi nathan.ro
/picozed
Signed-off-by: Nathan Rossi nathan.ro...@xilinx.com
---
arch/arm/cpu/armv7/zynq/Kconfig |4
arch/arm/dts/Makefile |1 +
arch/arm/dts/zynq-picozed.dts | 23 +++
configs/zynq_picozed_defconfig |6 ++
include/configs/zynq_picozed.h
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
-
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
, Mar 10, 2015 at 8:07 AM, Przemyslaw Marczak
p.marc...@samsung.com wrote:
Hello Nathan,
Now, I don't have too much time for this, but the only one you need is the
documentation and a time to analyze the responds for commands.
Please check this site:
https://www.sdcard.org/downloads/pls
On Fri, Feb 27, 2015 at 7:16 AM, Przemyslaw Marczak
p.marc...@samsung.com 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:
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_cmd
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.
$ sudo dd
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
On 12/13/10 18:47, Kumar Gala wrote:
Hopefully, Nathan can provide some input on this.
It is required by the C and C++ standards.
nathan
--
Nathan Sidwell:: http://www.codesourcery.com :: CodeSourcery
___
U-Boot mailing list
U-Boot
On 12/13/10 21:26, Wolfgang Denk wrote:
Dear Nathan,
In message4d066e11.9000...@codesourcery.com you wrote:
Hopefully, Nathan can provide some input on this.
It is required by the C and C++ standards.
Could you please provide a link? Not that I don't believe you, but
I'd like
=98312, limit=7
EXT2-fs error (device ram0): ext2_get_inode: unable to read inode block
- inode=12289, block=49155
attempt to access beyond end of device
ram0: rw=0, want=98312, limit=7
...
Thanks,
Nathan French
___
U-Boot mailing list
U-Boot
to ethernet devices. I see that both the 88E and the
DP83xxx devices use MII. Does this mean the DP83640 may just work as
is?
Thanks,
Nathan French
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
101 - 116 of 116 matches
Mail list logo
