lucascastro has joined #beagle
GenTooMan has quit [Ping timeout: 264 seconds]
set_ has quit [Remote host closed the connection]
GenTooMan has joined #beagle
GenTooMan has quit [Excess Flood]
yCrazyEdd has quit [Ping timeout: 244 seconds]
GenTooMan has joined #beagle
set_ has joined #beagle
lucascastro has quit [Ping timeout: 265 seconds]
behanw has joined #beagle
thinkfat has joined #beagle
thinkfat_ has quit [Ping timeout: 260 seconds]
vagrantc has quit [Quit: leaving]
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
buzzmarshall has quit [Quit: Konversation terminated!]
brook has quit [Remote host closed the connection]
ikarso has joined #beagle
otisolsen70 has joined #beagle
behanw has quit [Quit: Connection closed for inactivity]
rob_w has joined #beagle
GenTooMan has quit [Ping timeout: 244 seconds]
akaWolf has quit [Ping timeout: 268 seconds]
<jfsimon1981> Good morning
<jfsimon1981> Yes it more than enough, the program is a few 100 k maybe
<jfsimon1981> Ok so the console 1 Gb image
otisolsen70_ has joined #beagle
otisolsen70 has quit [Ping timeout: 264 seconds]
GenTooMan has joined #beagle
otisolsen70_ has quit [Read error: Connection reset by peer]
otisolsen70_ has joined #beagle
otisolsen70_ has quit [Quit: Leaving]
Shadyman has quit [Remote host closed the connection]
LetoThe2nd has quit [Quit: WeeChat 3.5]
akaWolf has joined #beagle
ft has quit [Quit: Lost terminal]
jfsimon1981 has quit [Remote host closed the connection]
florian has joined #beagle
jfsimon1981 has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
Guest62 has joined #beagle
Guest62 has quit [Client Quit]
insurgent has quit [Ping timeout: 244 seconds]
insurgent has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
jfsimon1981 has joined #beagle
akaWolf has quit [Ping timeout: 264 seconds]
lucascastro has joined #beagle
Guest60 has joined #beagle
jfsimon1981_b has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
Beagle45 has joined #beagle
<jfsimon1981_b> zmatt
<jfsimon1981_b> Matt, one question, i'm done with the process, do you think that way's gonna be all right ? I used a TI tool from debian console image:
<jfsimon1981_b> sudo apt update && sudo apt install bb-beagle-flasher
<jfsimon1981_b> sudo beagle-flasher
<jfsimon1981_b> Very simple, seems to be doing good job so far.
<jfsimon1981_b> Final install is about 600 meg
<Beagle45> Hi there,I'm new to BBB and I try to build from scratch u-boot.
<Beagle45> but I can't have the u-boot console instead I've
<Beagle45> U-Boot SPL 2022.07-rc6 (Sep 21 2022 - 11:33:02 +020)
<Beagle45> Trying to boot from MMC1
<Beagle45> Anyone have an idea ?
akaWolf has joined #beagle
brook has joined #beagle
Beagle4589 has joined #beagle
SJFriedl has quit [Read error: Connection reset by peer]
Beagle45 has quit [Ping timeout: 252 seconds]
Beagle4589 is now known as Beagle45
rob_w has quit [Quit: Leaving]
brook has quit [Remote host closed the connection]
SJFriedl has joined #beagle
Steve__ has joined #beagle
<zmatt> Beagle45: I'd generally be suspicious of any sort of tutorial or other documentation dating from 2014
<Beagle45> an it's boot from the sd to the EMMC
<Beagle45> thx for the answer
<zmatt> this is the tool used to build the official u-boot for beagleboard.org images: https://github.com/RobertCNelson/Bootloader-Builder
<zmatt> (though I have no idea how it works)
<jfsimon1981_b> ok
<jfsimon1981_b> I'll get it through
<Beagle45> good to know
<Beagle45> jfsimon1981_b
<Beagle45> good luck
<jfsimon1981_b> I ran it from the 1 GB debian console, i think it instralled an image of it into the emmc
<jfsimon1981_b> which is perfect in this case.
brook has joined #beagle
<Beagle45> Anyone know how to wipe the emmc on the board ??
<jfsimon1981_b> You probably run from microsd to do that
<jfsimon1981_b> burn the debian console for example into it and boot into it
<jfsimon1981_b> (press the boot switch button before poweruing up until it start to boot into the usd)
<Beagle45> jfsimon1981_b Okay thx but I'm talking about the emmc memory. I want to wipe this one
<jfsimon1981_b> exactly
<jfsimon1981_b> you run the OS from microsd then you can wipe it, when you'll run from microsd you can access and write/erase the other one, emmc.
<jfsimon1981_b> check slots with lsblk
<Beagle45> ah okay I did'nt understand thanks
<jfsimon1981_b> right
Beagle45 has quit [Quit: Client closed]
Guest60 has quit [Quit: Client closed]
Guest60 has joined #beagle
Guest60 has quit [Client Quit]
Beagle45 has joined #beagle
<Beagle45> I have a last newbie question.
<Beagle45> I built the kernel and then i try to boot on it it's say
<Beagle45> U-Boot SPL 2022.04 (Sep 20 2022 - 14:54:58 +0200)
<Beagle45> Trying to boot from MMC1
<Beagle45> U-Boot 2022.04 (Sep 20 2022 - 14:54:58 +0200)
<Beagle45> CPU  : AM335X-GP rev 2.1
<Beagle45> Model: TI AM335x BeagleBone Black
<Beagle45> DRAM:  512 MiB
<Beagle45> Core:  150 devices, 14 uclasses, devicetree: separate
<Beagle45> WDT:   Started wdt@44e35000 with servicing (60s timeout)
<Beagle45> NAND:  0 MiB
<Beagle45> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
<Beagle45> Loading Environment from FAT... Unable to use mmc 0:1...
<Beagle45> <ethaddr> not set. Validating first E-fuse MAC
<Beagle45> Net:   eth2: ethernet@4a100000, eth3: usb_ether
<Beagle45> Hit any key to stop autoboot:  0
<Beagle45> ** Invalid partition 2 **
<Beagle45> switch to partitions #0, OK
<Beagle45> Anyone have an idea why ??
<zmatt> Beagle45: please don't spam multi-line pastes into chat, use a paste service like pastebin.com to share logs
<Beagle45> Sorry :( I don't use much irc
<zmatt> also, I don't know what the default boot script of whatever u-boot you're using looks like, but nothing you've pasted looks like a real error to me
<zmatt> like, not being able to load environment is fine and normal (in fact, persistent environment is disabled in beagleboard.org's u-boot)
<zmatt> and my guess would be it probably gave the "invalid partition 2" error while trying to scan for partitions
<Beagle45> I cut to avoid too many lines
<Beagle45> The complete one
<Beagle45> and okay I'll check to this direction
<Beagle45> thx
<zmatt> yeah dunno, it looks like it's trying all sorts of things that don't make sense
<zmatt> why are you trying to build a custom u-boot anyway?
<Beagle45> it's to learn form scratch how things work
<Beagle45> using builtin tools it's easier but I can't really understand how it's work
<zmatt> if you want to understand how the boot flow works on a standard beagleboard.org image you may want to instead focus on understanding what the boot script of its u-boot does. merely reproducing an u-boot build doesn't seem particularly insightful to me
<zmatt> if it's of interest, here's its default environment, reformatted to looks more like a normal shell script (for improved readability): https://pastebin.com/Kt1rUe5V
<zmatt> the entrypoint is bootcmd
<Beagle45> zmatt okay thanks
<jfsimon1981_b> Matt thanks for all your help, i'll see how that goes on now, just monitoring the lab device and client will test it too, they have 2 units.
<jfsimon1981_b> I run them on reliable emmc and they have 1 gig free so should be good for long time, probably lifetime of the device.
<jfsimon1981_b> The TI tool when run from debian console image will make an ext4 partition, copy the microsd into to, so it's really installing the content of microSD currently mounted into the emmc. I end up putting all installatin files into the emmc, run safewrite, power cycle, flash, then restart from emmc and finish installation from it.
<zmatt> jfsimon1981_b: the flasher tool isn't a TI tool
<jfsimon1981_b> Makes a 1.8 gig ready for final installation and test.
<jfsimon1981_b> Yep ok. I though Robert Nelson is from TI
<zmatt> nope
GenTooMan has quit [Ping timeout: 264 seconds]
<jfsimon1981_b> yes all right
<jfsimon1981_b> but it works great
<jfsimon1981_b> i'll start with it
GenTooMan has joined #beagle
<Beagle45> jfsimon1981_b Felicitations :party:
<jfsimon1981_b> Sometime later i'll run reliability tests with a bb power up/off randomly, i want to see at which point the filesystem gets corrupted if at all
GenTooMan has quit [Ping timeout: 244 seconds]
<jfsimon1981_b> I'll have a device to randomly power off and recycle it.
GenTooMan has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
Beagle45 has quit [Quit: Client closed]
lucascastro has quit [Remote host closed the connection]
brook has quit [Remote host closed the connection]
vagrantc has joined #beagle
mag has quit [Remote host closed the connection]
mag has joined #beagle
GenTooMan has quit [Ping timeout: 260 seconds]
GenTooMan has joined #beagle
brook has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
ft has joined #beagle
Shadyman has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
ikarso has joined #beagle
brook has quit [Read error: Connection reset by peer]
brook has joined #beagle
LetoThe2nd has joined #beagle
<LetoThe2nd> NishanthMenon: i keep on forgetting which machine in meta-ti-bsp shall be used for the bbai64. can you kick my memory please? ;-)
<zmatt> j721e-something
<zmatt> LetoThe2nd: almost certainly j721e-evm
<zmatt> if there's nothing bbai64-specific
<zmatt> having said that, shouldn't it have a bbai64-specific config to select the right dtb?
<jfsimon1981_b> Matt i think you throw all logs away, be aware there's a tweak file at /etc/logrotate.d/rsyslog so that you can keep and rotate logs more often to reduce waste space.
<zmatt> jfsimon1981_b: rsyslog is one of the first things I remove from a system
<jfsimon1981_b> I won't throw away logs at the moment, but i replaced the rotate weekly by daily for some of them.
<jfsimon1981_b> Ok
<jfsimon1981_b> By removing it you don't get any log then ?
<zmatt> rsyslog is redundant, systemd-journald already handles logging. by default on beagleboard.org images it doesn't log persistently (i.e. logs are in ram only) which is also what I prefer, but you can easily enable persistent journal if desired
<jfsimon1981_b> in my case i have auth logs a lot
<jfsimon1981_b> because program calls sudo. That pollutes the filesystem
<zmatt> having a program call sudo sounds like a terrible kludge anyway, sudo is meant to be used by people, not by programs
<jfsimon1981_b> when you remove rsyslog what does it change ?
<zmatt> rsyslog takes configurable subsets of the same stuff that's logged to journal, and writes it to logfiles on eMMC
<jfsimon1981_b> yes i have to change that too, i'm using i2c command, i did'nt implement properly the main program yet so that was a quick fix.
<zmatt> I don't want logs to be written to eMMC, and I don't need these redundant legacy logs either way
<jfsimon1981_b> ok like when removed it won't go into the drive then ?
<jfsimon1981_b> Got to testit that sounds better once the system will be tested all right
<zmatt> I mean, you do you, but there's really no good reason for rsyslog anymore... not just not in production, but also not in development/testing, since journal is already keeping the exact same logs
<zmatt> (though like I said, journal on beagleboard.org images is non-persistent by default but you can easily change it to persistent if desired during development/testing, with configurable limits)
<jfsimon1981_b> ok
<jfsimon1981_b> when removing this file you don't get logs ?
<jfsimon1981_b> written to /var/log is it right ?
<zmatt> the only reason rsyslog is installed is to accomodate people who are too lazy to learn how to use journalctl to get logs from journal :D
<zmatt> rsyslog is what's writing logs in plain text to various files in /var/log/ yes
<zmatt> journal is queried using journalctl
<jfsimon1981_b> ok, so once removed it logs to ram only
<zmatt> yes, unless you enable persistent journal (by creating the directory /var/log/journal/ )
<jfsimon1981_b> i progably need to go that way long term
<jfsimon1981_b> i don't like the filesystem being written too much
<jfsimon1981_b> Ok
indigaz0 has joined #beagle
<jfsimon1981_b> Logs are'nt useful for your purpose ?
indigaz has quit [Ping timeout: 265 seconds]
indigaz0 is now known as indigaz
Steve__ has quit [Quit: Leaving]
lucascastro has joined #beagle
<zmatt> jfsimon1981_b: persistent logs on emmc? not really no, they're just pointless emmc writes
<zmatt> and like I said (more than once) if I had a need for persistent logs in some situation I can just make journal persistent on that particular device
<zmatt> I've never felt a need to do that though
<jfsimon1981_b> yes i understood it
<jfsimon1981_b> read you
<jfsimon1981_b> i'll get the logs enable for a while, they cycle, just tune it for a week instead of a month, in case something goes wrong i can debug it
<NishanthMenon> zmatt: LetoThe2nd - Sorry, I dont think we have had a chance to merge the patches in TI mainline kernel atm (upstream first rule).. but we could probably post a patch to use the beagleboard kernel instead for a ai64 build
lucascastro has quit [Remote host closed the connection]
ikarso has quit [Quit: Connection closed for inactivity]
brook has quit [Remote host closed the connection]
nparafe has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
nparafe has joined #beagle