<LeSpocky>
is it possible to make arithmetic calculations in u-boot scripts?
<LeSpocky>
(add an offset to a memory address)
GNUtoo has quit [Read error: Connection reset by peer]
GNUtoo has joined #u-boot
<LeSpocky>
I think 'setexpr' should work
prabhakarlad has quit [Quit: Client closed]
torez has joined #u-boot
akaWolf has quit [Ping timeout: 245 seconds]
akaWolf has joined #u-boot
hanetzer has quit [Ping timeout: 245 seconds]
hanetzer has joined #u-boot
Gravis has joined #u-boot
Gravis has quit [Ping timeout: 245 seconds]
camus has quit [Quit: camus]
pratyush has quit [Quit: Connection closed for inactivity]
hanetzer has quit [Ping timeout: 252 seconds]
hanetzer has joined #u-boot
prabhakarlad has joined #u-boot
vfazio has joined #u-boot
akaWolf has quit [Ping timeout: 245 seconds]
indy has quit [Ping timeout: 268 seconds]
indy has joined #u-boot
akaWolf has joined #u-boot
tsraoien has joined #u-boot
vfazio has quit [Read error: Connection reset by peer]
vfazio has joined #u-boot
macromorgan has joined #u-boot
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #u-boot
<rfs613>
crb_: does your dts file(s) use #include statements? if so, you need to run them through cpp (the C pre-processor) before using dtc.
<crb_>
rfs613: yes that was confusing, on my platform dtc supports /include/ natively not #include
<crb_>
rfs613: thank you!
<rfs613>
crb_: sorry if I added to the confusion... but the error you reported typically means you have a node reference like &ttc0 { stuff-goes-here; } and dtc cannot find the actual tty0 node, because it has been defined in an #included file.
Gravis has joined #u-boot
<crb_>
rfs613: no no, you were spot on. I came to that conclusion about 4 AM and realized that my etc was not issuing an error on the #include "blah" file but was issuing the error I pasted for node that were in the include file which wasn't processed. I changed from #include to /include/ and things just worked
<crb_>
rfs613: I didn't mean that you comment was confusing, but rather the problem was confusing since the bad include line wasn't flagged
<rfs613>
crb_: note that you can get the u-boot makefiles to run dtc for you (along with cpp etc). The easiest way is "make dtbs", which in turn means you have to add your dtb names to arch/arm/dts/Makefile (or whichever architecture you're on).
<crb_>
rfs613: yes I have u-boot building and working fine. I was building custom dtb files for the OS I'm using that have custom hardware I'm designing so I want to build the dtb as part of the driver build framework for that OS
<crb_>
rfs613: the problem was the dtc on my os is slightly different than the one used to build u-boot on my os and I go bit by this difference for a little bit.
<rfs613>
crb_: okay ;-)
<crb_>
rfs613: but I do thank you for responding. I could have been stuck there forever except I notice my dtb built in my OS was WAY smaller than the u-boot dtb when it should have been larger since it's more complete
<rfs613>
crb_: welcome.. the channel has been fairly quiet lately, I suspect a lot of folks are off on summer holidays...
persmule has quit [Ping timeout: 268 seconds]
persmule has joined #u-boot
Xeroine has quit [Ping timeout: 245 seconds]
vagrantc has joined #u-boot
apritzel has quit [Quit: Leaving]
jagan has joined #u-boot
Gravis has quit [Ping timeout: 245 seconds]
___nick___ has joined #u-boot
___nick___ has quit [Client Quit]
___nick___ has joined #u-boot
prabhakarlad has quit [Quit: Client closed]
prabhakarlad has joined #u-boot
vfazio has quit [Read error: Connection reset by peer]