<set_>
There is a script in there that handles the error of my source directly going to the else statement. I can now use if and elif.
<set_>
So, I input an integer. I then get feedback. And...my stepper makes a move in a loop for one go around.
<set_>
Before...the error/bug was that my catchy else statement kept ruining my good time.
<set_>
Slowly and surely, I will make something more complicated. For now, this is all I have currently.
<set_>
Oh...I was actually calling empty assignments instead of calling my input to make an output.
Shadyman has quit [Remote host closed the connection]
Raajeshwar has joined #beagle
<Raajeshwar>
Hi, I am using Beaglebone AI board. Whenever I connect the SD card and boot it, the content of the board is flashed to card and not the other way around. Board is not booting (with or without SD card). Can anyone help me on this?
outrageous_ has quit [Ping timeout: 260 seconds]
Raajeshwar has quit [Quit: Client closed]
outrageous has joined #beagle
Raajeshwar has joined #beagle
set_ has quit [Ping timeout: 260 seconds]
<zmatt>
Raajeshwar: that sounds like you changed the /boot/uEnv.txt config file on the eMMC to turn *it* into a flasher
<zmatt>
however regardless of the contents of eMMC, the BBAI will still always prefer to boot from SD card over booting from eMMC, so if it's not booting from SD card then your SD card isn't bootable
<zmatt>
make sure you have a correct image, and use Balena Etcher to flash it to sd card
<Raajeshwar>
Thank you zmatt. Yes I did change the file. But now couldn't get into it.
<zmatt>
that's because you made eMMC effectively unbootable by turning it into a flasher
<Raajeshwar>
Used this image: bone-debian-9.9-lxqt-armhf-2019-08-03-4gb.img.xz
<zmatt>
that's not an image for the BBAI
<Raajeshwar>
am57xx-debian-10.3-iot-tidl-armhf-2020-04-06-6gb.img.xz Will this work?
<Raajeshwar>
I mean, will this image get me in to the board instead of getting flashed again?
<zmatt>
if you boot a normal sd card image then it'll simply boot from sd card
<zmatt>
(after it's possible to mount the eMMC and undo your change in its /boot/uEnv.txt)
<Raajeshwar>
By the way "normal sd card image" means? There are list of images right?
<zmatt>
regardless of whether you want to flash to eMMC or boot from SD card, you'll want the latest (2020-04-06) AM5729 Debian IoT or IoT TIDL image (depending on whether you want TIDL or not)
<Raajeshwar>
Ok
<zmatt>
AM5729 Debian 10.3 2020-04-06 8GB SD IoT TIDL <-- that's a normal sd card image
<zmatt>
both of those are, as the name says, IoT TIDL images
<zmatt>
if you don't need TIDL then I'd suggest the non-TIDL image... though for some odd reason there's only a flasher image for that listed (AM5729 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher), I don't know why the normal (non-flasher) version of that is missing
<zmatt>
(the TIDL images use kernel 4.14, the non-TIDL images use kernel 4.19)
Raajeshwar has quit [Quit: Client closed]
Raajeshwar has joined #beagle
<Raajeshwar>
Yes I am not in need of TIDL
<zmatt>
unless you've got important data on eMMC you want to rescue, I'd suggest just getting the "AM5729 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" then and use it to reflash eMMC to a working state
<Raajeshwar>
Ok. I just want to turn the board working for now.
<Raajeshwar>
So I can use flasher image itself.
<zmatt>
if you download the flasher image, flash that onto sd card, and boot the BBAI, it should proceed to automatically reflash eMMC
<zmatt>
(once it's complete (beaglebone turns off), remove sd card and then it should boot normally again)
<Raajeshwar>
Ok. I will try it.
<Raajeshwar>
Thank you for your valuable inputs.
set_ has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
Raajeshwar has quit [Quit: Client closed]
buzzmarshall has joined #beagle
tigerxyz has joined #beagle
tigerxyz has quit [Client Quit]
tigerxyz has joined #beagle
tigerxyz53 has joined #beagle
tigerxyz53 has left #beagle [#beagle]
ghoulguy has joined #beagle
tigerxyz has quit [Quit: Client closed]
tigerxyz has joined #beagle
<tigerxyz>
Hi GoodM, How to disable firmware loading for HDMI: [ uboot_overlays: loading /lib/firmware/BB-HDMI-TDA998x-00A0.dtbo ]. I added disable_uboot_overlay_video=1. It didn't take
giort has joined #beagle
giort has quit [Client Quit]
tigerxyz has quit [Quit: Client closed]
<zmatt>
that is the correct way to disable that overlay, and it works on normal images
<zmatt>
can you pastebin the output of: sudo /opt/scripts/tools/version.sh
rcn-ee__ has quit [Quit: Leaving]
rcn-ee has joined #beagle
ghoulguy has left #beagle [#beagle]
florian has quit [Quit: Ex-Chat]
vagrantc has joined #beagle
vd has quit [Quit: Client closed]
vd has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
vagrantc has quit [Ping timeout: 252 seconds]
xet7 has quit [Remote host closed the connection]
xet7 has joined #beagle
xet7 has quit [Quit: Leaving]
vd has quit [Quit: Client closed]
vd has joined #beagle
zjason` has joined #beagle
zjason has quit [Ping timeout: 252 seconds]
ikarso has joined #beagle
<kveremitz>
technical question for those who use matrix .. is the beagleboard matrix 'bridged'/connected to matrix.org or whichever is the default 'service'?
<kveremitz>
[with apologies for vague use of technical terms]