ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
apritzel has quit [Ping timeout: 256 seconds]
Pali has quit [Ping timeout: 264 seconds]
Tokamak has quit [Ping timeout: 264 seconds]
Tokamak has joined #armlinux
leoy has joined #armlinux
furincleavagesit has joined #armlinux
furincleavagesit has quit [Quit: Textual IRC Client: www.textualapp.com]
tudorel has joined #armlinux
iokill has quit [*.net *.split]
mkl has quit [*.net *.split]
rfried has quit [*.net *.split]
palmer has quit [*.net *.split]
tmlind has quit [*.net *.split]
maz has quit [*.net *.split]
Sledge has quit [*.net *.split]
Sledge has joined #armlinux
palmer has joined #armlinux
mkl has joined #armlinux
tmlind has joined #armlinux
iokill has joined #armlinux
maz has joined #armlinux
marex has quit [*.net *.split]
marcan has quit [*.net *.split]
lag has quit [*.net *.split]
ajb-linaro has quit [*.net *.split]
kos_tom has quit [*.net *.split]
ziofork has quit [*.net *.split]
kos_tom has joined #armlinux
marex has joined #armlinux
marcan has joined #armlinux
ziofork has joined #armlinux
lag has joined #armlinux
ajb-linaro has joined #armlinux
guillaume_g has joined #armlinux
tre has joined #armlinux
apritzel has joined #armlinux
iivanov has joined #armlinux
Pali has joined #armlinux
matthias_bgg has joined #armlinux
apritzel has quit [Ping timeout: 256 seconds]
sszy has joined #armlinux
tiggilyboo has joined #armlinux
tiggilyboo has quit [Remote host closed the connection]
monstr has joined #armlinux
luispm has joined #armlinux
nsaenz has quit [Quit: Leaving]
nsaenz has joined #armlinux
alexels has joined #armlinux
<Xogium>
hmm how would one get the external ram to be recognized by linux on stm32f769 discovery kit ? Afaik, it only grabs the internal ram by default
<mort>
sounds like a devicetree thing?
apritzel has joined #armlinux
<Xogium>
possibly… Hmm
<Xogium>
never did that to any board before so why I'm asking
<mort>
I don't know anything about it either, I just feel I'd probably have to do a lot of digging into devicetree stuff to figure it out
djrscally has joined #armlinux
<Xogium>
hehe yeah, most likely
<ukleinek>
Xogium: after the bootloader set up the RAM you have to add a memory node
<Xogium>
er so not linux, bootloader work ?
<ukleinek>
Xogium: maybe. Linux won't setup the RAM, the bootloader probably does that already.
<ukleinek>
Xogium: in this case you only need a dt modification
<Xogium>
hmm
<Xogium>
I'm very bad with hexadecimal so frankly no idea what to put in there
<Xogium>
but alright
<jn>
/memory/reg usually
<jn>
you need hex in the addresses that you enter, sure, but you don't need to edit your devicetree in a hex editor
<Xogium>
yes that's the part I don't know
<mort>
writing hexadecimal is almost certainly not the actual problem you're having, but if it is, you can take whatever decimal value you want and search google for '<your number> to base 16'
<Xogium>
what reg and what addresses for memory size and etc
<jn>
the addresses of your external ram should, ideally, be in the board documentation
<Xogium>
heh I don't doubt that with st :)
<Xogium>
hmm the memory node in u boot extends to 0x1000000 currently… Maybe I can just extend it
<jn>
if it currently contains the range of the internal RAM, then i find it unlikely that increasing the end will work
<Xogium>
so I must add a second memory node ?
pg12 has quit [Ping timeout: 260 seconds]
<jn>
because it's not guaranteed that the external ram gaplessly follows the internal ram, in the physical address map of the chip
<Xogium>
right
<jn>
Xogium: no, a second pair of address/size in the reg attribute should be enough
<jn>
can you share the DT to make it easier to follow?
<Xogium>
so it does init the full ram… Interesting
<Xogium>
honestly thought it would not
<jn>
and the base address 0xC0000000 is external memory, as far as i understand Figure 2.2 in the reference manual (RM0410)
<Xogium>
so it doesn't use the internal ram at all then ?
<jn>
(because FMC connects to external memory, according to Fig. 1)
<jn>
Xogium: yep, that's how i read it
<Xogium>
right
<Xogium>
thanks for explaining that
<jn>
it might use the 144 kb of TCM, depending on kernel configuration, because TCM can be auto-discovered
<Xogium>
ironically now my board won't even boot or if it does, doesn't seem like it talks over st-link ? Usart1 is the default serial port, though
<jn>
("tightly coupled memory")
<Xogium>
I used proper baudrate, copied u-boot.bin in the internal flash and pressed reset, and there's nothing
<Xogium>
maybe u-boot for that board is broken
<Xogium>
sure wish boards had beepers instead of leds…
tudorel has quit [Quit: tudorel]
<ukleinek>
Xogium: beepers are also not the optimal thing. I have a customer board in a remote lab with a beeper. Great thing to annoy the coworkers who are in the office while not noticing there is a problem on the board that makes noise :-)
elastic_dog has quit [Ping timeout: 264 seconds]
<Xogium>
true, but in my case… Ugh
<Xogium>
sure would help
<Xogium>
I have no idea what state my board is currently in
<Xogium>
is it booted and just not talking ? Does it hang ? Does it not even start u-boot…
<Xogium>
mm pair of sighted eyes confirm there's 2 leds on board, both are fixed, green and red
<Xogium>
I assume red is power
<Xogium>
I mean its kind of difficult to debug when even st-link serial port is silent
ravan has joined #armlinux
prabhakarlad has quit [Quit: Client closed]
Amit_T has joined #armlinux
nsaenz has quit [Remote host closed the connection]
alpernebbi has quit [Ping timeout: 264 seconds]
nsaenz has joined #armlinux
alpernebbi has joined #armlinux
elastic_dog has joined #armlinux
tudorel has joined #armlinux
torez has joined #armlinux
tre has quit [Remote host closed the connection]
iivanov has quit [Quit: Leaving...]
elastic_dog has quit [Ping timeout: 250 seconds]
iivanov has joined #armlinux
manic_laughter has joined #armlinux
elastic_dog has joined #armlinux
manic_laughter has quit [Client Quit]
manic_laughter has joined #armlinux
manic_laughter has quit [Quit: Leaving]
manic_laughter has joined #armlinux
ravan_ has joined #armlinux
ravan has quit [Ping timeout: 260 seconds]
manic_laughter has quit [Quit: Leaving]
Amit_T has quit [Ping timeout: 265 seconds]
Amit_T has joined #armlinux
torez has quit [Ping timeout: 250 seconds]
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
System_Error has quit [Remote host closed the connection]
System_Error has joined #armlinux
Tokamak has joined #armlinux
torez has joined #armlinux
monstr has quit [Remote host closed the connection]
<HdkR>
Is `arch/arm/tools/syscall.tbl` the location to figure out which syscall number corresponds to which name of syscall? I want to make sure my tooling pulls from the correct source of truth
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Tokamak has joined #armlinux
nsaenz has quit [Quit: Leaving]
<geertu>
HdkR: #include <asm/unistd.h>?
nsaenz has joined #armlinux
<HdkR>
Might be fine if I wasn't programmatically generating some definitions
<geertu>
HdkR: Then arch/arm/tools/syscall.tbl should be fine
ravan__ has joined #armlinux
ravan_ has quit [Ping timeout: 268 seconds]
milkylainen has joined #armlinux
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<HdkR>
Alright, sounds good.
tudorel has quit [Quit: tudorel]
guillaume_g has quit [Quit: Konversation terminated!]
matthias_bgg has quit [Quit: Leaving]
elastic_dog has quit [Ping timeout: 250 seconds]
pg12 has joined #armlinux
Turingtoast has joined #armlinux
Tokamak has joined #armlinux
elastic_dog has joined #armlinux
alexels has quit [Quit: WeeChat 3.3]
elastic_dog has quit [Quit: elastic_dog]
elastic_1 has joined #armlinux
elastic_1 has quit [Client Quit]
elastic_dog has joined #armlinux
Tokamak has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Turingtoast has quit [Quit: My iMac has gone to sleep. ZZZzzz…]