brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 252 seconds]
hnv has joined #beagle
brook has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 246 seconds]
renrelkha has quit [Quit: bye]
renrelkha has joined #beagle
ikarso has joined #beagle
renrelkha has quit [Quit: bye]
renrelkha has joined #beagle
MaazSk has joined #beagle
MaazSk66 has joined #beagle
MaazSk66 has quit [Client Quit]
<MaazSk>
Hi, I need help with beagle board, I am new to the community and I don't know how to program it I want a simple led blinking code can anyone please help me? I am using a beaglebone black board
<MaazSk>
Before moving forward do I need to update its firmware?
MaazSk has quit [Ping timeout: 244 seconds]
hnv has quit [Ping timeout: 244 seconds]
Shadyman has quit [Remote host closed the connection]
<jfsimon1981>
you can probably connect to it through the IP
<jfsimon1981>
I believe 192.168.7.2 if on USB or assigned by DHCP if on you lan
<jfsimon1981>
From there you'll find tutos and can control a bit through Python and cloud9
<jfsimon1981>
You can also login with ssh and pass commands to GPIO or write a program too.
<zmatt>
they left
<jfsimon1981>
Ok
set_ has quit [Ping timeout: 260 seconds]
set_ has joined #beagle
otisolsen70 has joined #beagle
florian has joined #beagle
johanhenselmans has quit [Quit: johanhenselmans]
ft has quit [Quit: leaving]
set_ has quit [Remote host closed the connection]
johanhenselmans has joined #beagle
johanhenselmans has quit [Remote host closed the connection]
johanhenselmans has joined #beagle
Guest6068 has joined #beagle
<Guest6068>
Hello,
SJFriedl has quit [Quit: Leaving]
<Guest6068>
zmatt sorry I left, the last few days the internet company I use is giving me tons of problems and giving lot of instability. So I read the logs of yesterday, so you say to do what I want, it's not that hard?
<Guest6068>
From what I could gather, I need to modify a few of the files that manage the booting process, but I am still in the process of identifying the files, what do I need to modify and how to modify them
SJFriedl has joined #beagle
<zmatt>
Guest6068: you're the pocketbeagle uart0 person? (picking a better name than "Guest" would be helpful)
<Guest6068>
yeah, i am, I will change it
Guest6068 has quit [Quit: Client closed]
<zmatt>
I'm pretty sure only a single source file of u-boot needs to be modified, I mentioned which one in the irc log
<zmatt>
I don't think any DT modification is required
<uart0_person>
yeah I missed between changing the names
<zmatt>
yeah, for future reference, you don't need to disconnect/reconnect to change name, you can use the /nick command instead
<uart0_person>
oh ok
<uart0_person>
didn't you say I need to reproduce the uboot?
<zmatt>
I mean, to build a modified version of the beagleboard.org u-boot you obviously need to be able to build an unmodified one in the first place
<zmatt>
I think rcn-ee has a guide for that somewhere but I don't remember where
<uart0_person>
oh, he answered my answer about this problem in the forum, but he only said it was simple, just patch it and recompile and then didn't say anything more haha
<uart0_person>
my question*
<zmatt>
I don't really have time to go digging myself right now, I'm at work
<uart0_person>
ok, I understand
<uart0_person>
don't want to cause any bother
<uart0_person>
I am already immensely just to have someone paying attention to my dilemma
<uart0_person>
immensely grateful*
set_ has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
buzzmarshall has joined #beagle
<set_>
Blah!
<set_>
I just figured out what happened to all my work. It was a connection issue. So, it was a connection in my brain that needed to be made. Notes, remembering, or whatever, I had nothing. Now, back in it to win it!
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
brook has quit [Ping timeout: 260 seconds]
ikarso has quit [Quit: Connection closed for inactivity]
brook has joined #beagle
uart0_person has quit [Ping timeout: 244 seconds]
alan_o has quit [Quit: Leaving]
alan_o has joined #beagle
alan_o has quit [Client Quit]
alan_o has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
uart0_person has joined #beagle
ft has joined #beagle
uart0_person has quit [Ping timeout: 244 seconds]
ft has quit [Remote host closed the connection]
ft has joined #beagle
alan_o has quit [Ping timeout: 272 seconds]
brook has quit [Read error: Connection reset by peer]
<zmatt>
(*uart0 will still be enabled and have its pins muxed by default)
<uart0_person>
right now, I have pocketbeagle with a sd already flashed
<uart0_person>
I thought if I followed the guide I would need to reflash it
<zmatt>
you don't follow the guide, you just follow the guide to build an u-boot and install that onto your existing image (and then hope it still works ;) ... do you have a debian host system (in a vm if need be) to build u-boot?
<uart0_person>
yeah, I do
<uart0_person>
Ok, I download the u-boot, do "I think it may suffice to just replace occurrences of ttyS0 by ttyS1 in include/configs/am335x_evm.h", build the u-boot, and do sudo systemctl disable serial-getty@ttyS0.service?
<zmatt>
ok, so you can also use that to make a backup of the first 4MB of your sd card (which is where u-boot lives) and install your new u-boot
<zmatt>
disabling serial-getty@ttyS0.service is something you need to do to prevent the kernel from spawning a getty there, it has nothing to do with u-boot
<uart0_person>
ok
<uart0_person>
shouldn't I also modify something in the kernel files? Since the UART index for Linux console is specified in U-Boot env 'bootargs
<zmatt>
once you disable that you can't use the serial port to login anymore, but you still get early boot messages
<zmatt>
u-boot tells the kernel what the console is, so changing u-boot suffices
<uart0_person>
ok, how do you know exactly the file to make the changes?
<zmatt>
I do and I just told you
<zmatt>
10 minutes ago
<uart0_person>
Is from experience? Is there a logic ?I spent the last few days trying to figure
<zmatt>
oh "how"
<zmatt>
I misread that as "do you know..."
<uart0_person>
I have to stop sending messages one at time
<uart0_person>
and send them together so this doesn't happen anymore
<zmatt>
I dunno, I just know a lot as a result of having been around and using beaglebones for quite a while ;)
<zmatt>
you're fine, I just misread it
<zmatt>
I checked the patch that's done on top of u-boot for beagleboard.org images since that includes customization of the default environment (which includes u-boot's boot scripts)
<zmatt>
so I could immediately see in which file that's done, since I do generally forget which file exactly that resides in
<uart0_person>
It's that I am starting in this embedded area, and while researching I saw so many people saying a lot of command lines and knowing so many possible files to where the problem maybe, and I struggling with something so basic makes me think maybe I am too dumb for these things
<zmatt>
it just takes time and experience to absorb these random bits of arcane knowledge
<zmatt>
the main problem here is that (by unfortunately using the uart0 pins for your pcb) you painted yourself into a corner where you need some relatively obscure knowledge
<zmatt>
generally speaking people don't build a custom u-boot ;)
<uart0_person>
got it
<uart0_person>
what does "I checked the patch that's done on top of u-boot for beagleboard.org images since that includes customization of the default environment (which includes u-boot's boot scripts)" means?
<uart0_person>
that the uboot already uses a patch that customizes the uboot for the specific board?
<zmatt>
brb
uart0_person21 has joined #beagle
uart0_person21 has quit [Client Quit]
uart0_person67 has joined #beagle
uart0_person has quit [Ping timeout: 244 seconds]
uart0_person has joined #beagle
<zmatt>
uart0_person67: beagleboard.org images don't use mainline u-boot, they have some patches on top to provide some custom functionality for these images, e.g. for DT overlays and cape autodetection
uart0_person67 has quit [Ping timeout: 244 seconds]
<uart0_person>
got it
<zmatt>
part of this is done by customizing u-boot's environment variables, which are used for its built-in shell which executes the boot script... that boot script is itself also stored in environment variables (since u-boot's shell doesn't really support shell functions)
<zmatt>
these environment variables (or at least their default values) are constructed in a header, which is the one you need to patch
<uart0_person>
the one said right, this one include/configs/am335x_evm.h
<zmatt>
yeah
<uart0_person>
ok, I make a backup of the u-boot already present in my pocket before anything;
<uart0_person>
I download the u-boot, change the header to another uart;
<uart0_person>
Do the steps to compile;
<uart0_person>
and then install the compiled uboot to my pocket;
<uart0_person>
Is that it?
<zmatt>
yeah, to backup it suffices to just backup the first 4 MB of the sd card... u-boot consists of two files: MLO and u-boot.img, the former is installed at sector offset 256 (i.e. 128K from the start of the disk) and the latter at sector offset 768 (i.e. 384K from the start of the disk)
<uart0_person>
this backup
<zmatt>
oh it seems in this u-boot version the second file is named u-boot-dtb.img ... based on the instructions to install u-boot later on that forum page you linked
<uart0_person>
ok
<zmatt>
dd if=DEVICE of=backup.img bs=4M count=1
<zmatt>
(where DEVICE is the sd card)
<uart0_person>
my god you already answered what I was going to ask
<zmatt>
of course you can alternatively make a backup of the whole card if you want to
<uart0_person>
I use lsblk to figure out the name of the sd card, right?
<zmatt>
for example
<zmatt>
try to avoid accidently writing to the boot disk of your host machine ;)
<uart0_person>
this mean the machine connected to pocket
<zmatt>
the machine you're using to backup and modify your sd card... which is presumably also the machine you're using to compile u-boot
<uart0_person>
ok, that's what I thought
<uart0_person>
sorry for the many questions, I prefer to be through so there aren't unknown variables
<uart0_person>
I think for today my last question
<uart0_person>
following the guide I sent, the steps for installing the uboot
<uart0_person>
where they begin and where they end?I identified the part saying to install u boot and there are a few steps before this
<uart0_person>
ok, I compile the custom uboot, it generates these two files
<zmatt>
(it looks like those commands assume you're in the parent dir of the u-boot source tree)
<uart0_person>
i place them inside uboot
<uart0_person>
and use these commands
<uart0_person>
while at uboot
<zmatt>
"./u-boot/" here is the u-boot source/build tree, in which those files are generated when you perform the build
<zmatt>
so if you're already in that dir you can just use if=MLO and if=u-boot-dtb.img
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
<uart0_person>
lets back up a bit.
brook_ has quit [Read error: Connection reset by peer]
<uart0_person>
In my ubuntu machine, I download the uboot from the guide and then change that header file and then follow the steps to compile.
<uart0_person>
before installing anything, I make a copy of the uboot inside my sd card somewhere.
<uart0_person>
Then I replace the uboot folder in my pocket with the one I generated in my ubuntu machine?
brook has joined #beagle
<zmatt>
what u-boot folder? you just install those two files (produced by the u-boot build) using those two dd commands, that's it
otisolsen70 has quit [Quit: Leaving]
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook_ has joined #beagle
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
<uart0_person>
I feel I am mixing things up
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
<uart0_person>
I am building the uboot outside the sd card
<uart0_person>
in the ubuntu machine
brook has joined #beagle
<uart0_person>
so i get those two files
<zmatt>
yes, and then you install them using those two dd commands
<zmatt>
(install them directly onto the sd card)
<uart0_person>
don't i have to transfer them to sd card before?
brook has quit [Read error: Connection reset by peer]
<zmatt>
what would be the point of doing that? they don't need to be files on the sd card, they need to be installed in a very specific way outside the filesystem, which is what those dd commands do
brook has joined #beagle
<uart0_person>
oh ok
<uart0_person>
I didn't realize you could do that
<zmatt>
they're installed in the space between the partition table and the rootfs partition
uart0_person has quit [Quit: Client closed]
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
uart0_person has joined #beagle
brook has joined #beagle
<uart0_person>
Hi, i am back,
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
<uart0_person>
I didn't knwo you could install something into pocket beagle from a external machine
<uart0_person>
that's why I was confused
<zmatt>
ehh, I'm assuming you have the sd card in your host machine of course
<zmatt>
for these steps
<zmatt>
not in the pocket beagle
<uart0_person>
ok, understood
<zmatt>
otherwise making a backup is useless since you wouldn't be able to restore it if the pocketbeagle fails to boot :P
<uart0_person>
ooooh, now I understand the backup commands too
<uart0_person>
i thought you were making a copy inside the sd
<uart0_person>
but it is also in the machine
<uart0_person>
i waa thinking it didn't make sense
<zmatt>
hehe, hopefully now everything makes more sense
<uart0_person>
yep
<uart0_person>
ok, the sd is connected to ubuntu machine, I make the backup, but not all of the sd card
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
<uart0_person>
i download the uboot, make the changes into header file
<zmatt>
I mean, feel free to backup the whole card if you want to
brook has quit [Read error: Connection reset by peer]
<uart0_person>
compile
<uart0_person>
and inside where the files are, i use the commands to install
<uart0_person>
then i turn om the pocket and see if it boots
<uart0_person>
on*
<zmatt>
if you're inside the directory where the files are (rather than the parent dir), be sure to change the dd commands accordingly (e.g. if=MLO instead of if=./u-boot/MLO)
<zmatt>
other than that, yep
brook has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
uart0_person has quit [Ping timeout: 244 seconds]
brook has quit [Remote host closed the connection]
<set_>
Hey guys. Sorry and not sorry about my odd presentation this morning. I am finally figuring out what it is that needs to take place for me to build an image. Phew.
<set_>
I lost it due to an old 'puter w/ random hardware. I just got it back! The old swing of things!
<set_>
FIY DIY!
brook has quit [Remote host closed the connection]