e in my serial port, that's why it appears like it hangs but I'm not
so sure about that.
I also defined the following inside my config file:
CONFIG_DEBUG_UART_PHYS=0xf8038200
CONFIG_DEBUG_UART_VIRT=0xf7038200
Any help would be appreciated.
On Fri, Mar 2, 2018 at 11:58 AM, Nicolas Ferre <nicolas
I found the problem. In my header file I was reading from eMMC device 1.
Not 0. That's why the operations with mmc worked in command line but did
not on startup.
Please correct me if I'm mistaken but I have a couple questions.
1) Do I need a partition in my eMMC in order to boot the Linux kernel?
ersion 5.0 document maybe it could bring
some insight on what is happening. The driver is supposed to match with any
eMMC but still.
On Tue, Feb 27, 2018 at 7:24 PM, Yang, Wenyou <wenyou.y...@microchip.com>
wrote:
>
> On 2018/2/28 0:55, Mariano Coromac wrote:
>
>> Hmmm, by se
Hmmm, by sequential number do you mean the Specification Version? This one
is correct.
Here's my eMMC info.
=> mmc info
Device: sdio-host@a000
Manufacturer ID: eb
OEM: 10d
Name: eMMC
Tran Speed: 5200
Rd Block Len: 512
MMC version 5.0
High Capacity: Yes
Capacity: 3.6 GiB
Bus Width: 4-bit
END:17
ARG 0x
MMC_RSP_R1,5,6,7 0x0900
Any guidance would be appreciated.
Thank you.
On Wed, Feb 14, 2018 at 3:27 PM, Mariano Coromac <mcoro...@stsa.info> wrote:
> Forget it guys, I just realized what was wrong.
> reg = <0xf8038200 0x200>
Forget it guys, I just realized what was wrong.
reg = <0xf8038200 0x200>;
Before it was
reg = <0xf8038200 0x100>;
So if anyone else (that wants to use the flexcom uart) asks you about this
now there's another thing you can point to.
If I encounter another problem or something I'll get back to you.
I think I found the root problem for this. I am using a flexcom uart. The
ones that are defined in sama5d2.dtsi are normal uarts, one can use those
definitions alongside the drivers to use uart0 to uart4.
I found a definition to use flexcom, here:
H it displays the following:
Class Probed Name
root[ + ]root_driver
simple_bus [ ]`-- ahb
mmc [ ]|-- sdio-host@a000
blk [ ]| `-- sdio-h...@a000.blk
mmc [ ]
Thank you very much. I expanded the malloc into a bigger number and now I
don't get those errors.
My remaining problem is that I can't seem to move the serial console or
console monitor (I don't know which term is better) into my flexcom1 usart.
It always keep saying:
No serial driver found
Thanks for the info. Apparently now the console is redirected but I keep
getting these driver errors:
bind node serial@f8038200
- attempt to match compatible string 'atmel,at91sam9260-usart'
- found match at 'serial_atmel'
Error binding driver 'serial_atmel': -12
For what I understand, the
With that one there is none, I had problems with the other one.
Right now I just want to know how the CONIG parameters like this one:
CONFIG_8xx_CONS_SMC1=
Apply to my SAMA5D2. I already have my debug uart working but not the
monitor console. Therefore I can't even print 'help'.
Also, I'm still
om one.
On Mon, Feb 12, 2018 at 8:59 AM, Marek Vasut <ma...@denx.de> wrote:
> On 02/12/2018 03:52 PM, Mariano Coromac wrote:
> > Hello, I was hoping you could help me out with something. I just have 2
> > main questions. I am using a SAMA5D27 and I've managed to port
> > AT91
Sorry, I tried to switch to the upstream repo but it gave some compiling
errors.
I am using the 409952795f8a28d3c266b2b8b2b9eccf46347601 commit from git://
github.com/linux4sam/u-boot-at91.git
___
U-Boot mailing list
U-Boot@lists.denx.de
redirect the debug uart into these usart?
Or do you think this has to do with my device tree?
atmel_usart.o does gets generated and the target is defined on the
makefiles.
Thank you, sorry if this has been asked before.
PD: I'm not using any commercial board, is a custom one.
--
Mariano Coromac <ht
14 matches
Mail list logo
