07:22 <Dudy> Hello guys

07:22 <Dudy> I am a newbie Beaglebone here, hola

07:33 <tbr> good moaning

07:37 <Dudy> How are you

07:42 <tbr> I'm fine, thanks

07:42 <tbr> if you have questions about your BBB, just go ahead and ask, and someone will answer sooner or later

07:43 <Dudy> oh, thanks. I will post here

07:44 <Dudy> So I just purchased BB Green Wireless, at first I can connect and operate it. I tried to update the linux packages via ssh, but update failed because of bonescript. I tried to reinstall bonescript, but not solving.

07:46 <Dudy> then I just think, just flash with SD Card. I followed the instruction, changed the commented thing said in instruction. and I choose the latest version for imaging to sdcard

07:48 <Dudy> I follow exactly how it written, hold on boot before powering, and release, and see it's running light pattern in progress. Then it turned off. Took out the sd card and turn BB on. but then after turn on not even wireless signal AP appear, the web is not working, and I put with UART to usb also not catch in PORT when I check.

07:49 <Dudy> I totally don't know what went wrong, but anyway, I couldn't connect it

07:50 <Dudy> What I got now is USR0-3 is light without any blinking.

07:50 <Dudy> WLAN and BLE light not flashing

07:51 <Dudy> I need help

08:17 <zmatt> Dudy74: if you use a flasher image you don't need to modify /boot/uEnv.txt

08:19 <zmatt> Dudy74: i.e. download the "AM3358 Debian 10.3 2020-04-06 4GB eMMC IoT Flasher" under "Flasher Debian images" on https://beagleboard.org/latest-images

08:19 <zmatt> write it to sd card using Etcher

08:20 <zmatt> if you boot the beaglebone from that, it should automatically proceed to flash to eMMC and it will then power off (after which you can remove the card and power it back on)

08:23 <zmatt> to boot the beaglebone from the sd card it usually suffices to just have the sd card inserted when you power it on (or reboot/reset), though in some rare cases (bootloader on eMMC is broken, very old, or otherwise incompatible with the system on SD card) this doesn't suffice in which case you can force the beaglebone to ignore eMMC and boot from SD card by holding down the S2 button (the one closest ...

08:23 <zmatt> ...to the sd card slot) while powering on it on (you can let go of the button once the power led turns on)

08:24 <zmatt> the getting-started guide should really be updated to recommend using a flasher image to reflash the eMMC

08:24 <zmatt> (it happens a bit too often that people make mistakes with the other method)

15:35 <Dudy> Yup, it start to work now, I can see it blinking normal, I can get the host running, and connect to UART. Now, the wifi is something that I can't connect from my computer, it says need password for network key and I don't know where actually the information

15:52 <zmatt> Dudy: default password of the wifi access point is BeagleBone, you can change the access point network name and password in /etc/default/bb-wl18xx

16:21 <Dudy> thanks

17:41 <Guest24> Hey guys, I am looking for a beagleboard product that has an integrated ADC, but with a large voltage tolerance. Any suggestions?

18:11 <zmatt> Guest24: define "large voltage tolerance"

18:14 <zmatt> the AM335x-based beaglebones have a max 1.8V adc voltage, iirc the beaglebone AI has an on-board ADC whose max voltage can be software-configured to 1.8V or 3.3V, the beagleboard-x15 has no ADC whatsoever

18:15 <zmatt> so your options are to scale your voltage (e.g. using a voltage divider if this is acceptable for the application, or an opamp otherwise) or use an external ADC

18:56 <Guest24> ±5V

18:56 <Guest24> I think my best route is to use a voltage divider circuit to step down this voltage range

19:44 <jkridner> NishanthMenon: on TDA4VM, can the MPU program the MCU peripherals? and/or can the MCU program the MPU peripherals?

19:48 <jkridner> NishanthMenon: the pinmux options on TDA4VM are making me .... emphatically unhappy.

20:06 <kveremitz> jkridner: I take it you're aware the bb images are stalled yes?! :) or is it Rob's domain..

20:06 <kveremitz> zmatt confirmed I wasn't seeing things yesterday :)

20:35 <zmatt> jkridner: as far as I know both sides can access peripherals on both sides by default (unless you deliberately setup firewalls to block this)