public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] v7_outer_cache_inval_range error on iMX6Q
Date: Thu, 23 Nov 2017 20:55:07 +0100	[thread overview]
Message-ID: <20171123205507.23d8411e@jawa> (raw)
In-Reply-To: <143368b6-6111-9dbf-5a73-f8e4b9c2d326@baylibre.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 2638 bytes --]

Hi Neil,

> Hi,
> 
> I'm having a strange issue while porting the DART-MX6 and it's
> carrier board to mainline U-Boot.
> 
> Everything works as expected except "fatls" where I get the following
> output :

Please look into:
http://patchwork.ozlabs.org/patch/831183/

IN short:

You may need to fix the code by using cache aware allocation
functions instead of calloc(), malloc().


BR,
Łukasz
> 
> => fatls mmc 0:1  
> CACHE: Misaligned operation at range [4f59dfc8, 4f59e7c8]
> CACHE: Misaligned operation at range [4f59dfc8, 4f59e7c8]
> ERROR: v7_outer_cache_inval_range - start address is not aligned -
> 0x4f59dfc8 ERROR: v7_outer_cache_inval_range - stop address is not
> aligned - 0x4f59e7c8 CACHE: Misaligned operation at range [4f59dfc8,
> 4f59e7c8] CACHE: Misaligned operation at range [4f59dfc8, 4f59e7c8]
> ERROR: v7_outer_cache_inval_range - start address is not aligned -
> 0x4f59dfc8 ERROR: v7_outer_cache_inval_range - stop address is not
> aligned - 0x4f59e7c8
> 
> 0 file(s), 0 dir(s)
> 
> But :
> => fatinfo mmc 0:1  
> Interface:  MMC
>   Device 0: Vendor: Man 000074 Snr 62aee901 Rev: 4.2 Prod: USD  \x10
>             Type: Removable Hard Disk
>             Capacity: 7695.0 MB = 7.5 GB (15759360 x 512)
> Filesystem: FAT16 "boot       "
> 
> And it contains :
>     41541   imx6q-var-dt6customboard.dtb
>   6535440   uImage
> 
> And even fatload works :
> => fatload mmc 0:1 $loadaddr uIMage  
> reading uIMage
> 6535440 bytes read in 322 ms (19.4 MiB/s)
> 
> Same for mmc0 (SDCard) and mmc1 (eMMC).
> 
> I tested against v2017.11 and master
> (16fa2eb95172e63820ee5f3d4052f3362a6de84e) with :
> gcc-linaro-4.9.4-2017.01-x86_64_arm-eabi
> gcc-linaro-7.1.1-2017.08-x86_64_arm-linux-gnueabihf
> 
> same behaviour.
> 
> And same behaviour when reverting the following :
> af609e3 fs/fat: Check malloc return values and fix memory leaks
> 09fa964 fs/fat: Fix 'CACHE: Misaligned operation at range' warnings
> 8df8731 fs/fat: Fix pathnames using '..' that lead to the root
> directory 2460098 fs/fat: Reduce stack usage
> 
> Do someone have an idea except disabling data cache ?
> 
> Thanks,
> Neil
> 



Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171123/385b7b0f/attachment.sig>

  reply	other threads:[~2017-11-23 19:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-23 15:18 [U-Boot] v7_outer_cache_inval_range error on iMX6Q Neil Armstrong
2017-11-23 19:55 ` Lukasz Majewski [this message]
2017-11-24  8:45   ` Neil Armstrong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171123205507.23d8411e@jawa \
    --to=lukma@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox