ChanServ changed the topic of #rust-embedded to: Welcome to the Rust Embedded IRC channel! Bridged to #rust-embedded:matrix.org and logged at https://libera.irclog.whitequark.org/rust-embedded, code of conduct at https://www.rust-lang.org/conduct.html
kpcyrd[m] has quit [Quit: Idle timeout reached: 172800s]
henrik_ has quit [Remote host closed the connection]
adamgreig[m] has quit [Quit: Idle timeout reached: 172800s]
crabbedhaloablut has joined #rust-embedded
emerent_ has joined #rust-embedded
emerent is now known as Guest7684
Guest7684 has quit [Killed (platinum.libera.chat (Nickname regained by services))]
emerent_ is now known as emerent
IlPalazzo-ojiisa has joined #rust-embedded
Ralph[m] has quit [Quit: Idle timeout reached: 172800s]
M9names[m] has quit [Quit: Idle timeout reached: 172800s]
explodingwaffle1 has quit [Quit: Idle timeout reached: 172800s]
emmanuelsearch[m has joined #rust-embedded
<emmanuelsearch[m> Barging in with job offers 😀 Several positions opened today at Inria to develop embedded Rust building blocks for the RIOT operating system code base. More info [here](https://recrutement.inria.fr/public/classic/en/offres/2023-07034).
<AdamHott[m]> Wondering if anyone could take a look at this main.rs of 27 lines. I included the problem description in the README.md and there are pictures in references -> images folder.
<Lumpio-> The links are 404 so either they're wrong or it's a private repo
<AdamHott[m]> oh thanks I'll make it public now!
<AdamHott[m]> ok it's public now!
<Lumpio-> My guess is that the pin is wrong - the pin numbers on many popular microcontroller boards don't necessarily correspond to the hardware pin numbers because whoever made them thought that would be simpler
<AdamHott[m]> Do you think I should just plug through all of the pins other than the 3V and 0Vs for that connection?
<Lumpio-> Try p0_02
<AdamHott[m]> In the code? or on the Edge Connector? or both?
<Lumpio-> In the code
<Lumpio-> I think p0_02 might correspond to the pin labeled "1" on that breakout according to this picture: https://images.elecfreaks.com/mageplaza/blog/post/uploads/2017/11/5-1.jpg
<AdamHott[m]> Ooh wow this is super helpful. Is that for the micro:bit V2?
<Lumpio-> I think this might be for V1, it doesn't say
<Lumpio-> https://tech.microbit.org/hardware/edgeconnector/#pins-and-signals this is probably a more official list
<Lumpio-> So I guess for V2 it might be p0_03?
<Lumpio-> If you click "V2" the table should show the hardware pin names under "MCU" and the breakout pin numbers under "s/w"
<AdamHott[m]> Ah yes!
<AdamHott[m]> This makes sense!
<Lumpio-> Looks like they totally rearranged the pins between versions for some reason
<AdamHott[m]> Yeah, must have been added functionality
<AdamHott[m]> Hey thanks so much for your help!
<Lumpio-> Did you get it to work?
<AdamHott[m]> I'll have to clear the table and reconnect! Will take but a sprig of a moment.
<Lumpio-> Well, good luck!
<AdamHott[m]> THANK YOU!
<AdamHott[m]> <Lumpio-> "Well, good luck!" <- It works! Yayy!
<Lumpio-> Nice!
johannes[m] has quit [Quit: Idle timeout reached: 172800s]
<Lumpio-> You'll find that the same pin can sometimes have 3 or more numbering schemes - one based on hardware port numbers, one based on physical chip pin numbers, and one based on whatever connector or board you're using
<Lumpio-> Can get confusing at times
<AdamHott[m]> How do you sort through that, just trial and error?
cyrozap_ has quit [Quit: ZNC 1.8.2+deb3.1 - https://znc.in]
cyrozap has joined #rust-embedded
Lumpio[m] has joined #rust-embedded
<Lumpio[m]> Adam Hott With documentation - like the table I linked, chip datasheets and sometimes even schematics
<Lumpio[m]> Sometimes people will unfortunately just talk about "pin 3" and then you'll have to make an educated guess as to which numbering it is.
<JamesMunns[m]> <AdamHott[m]> "How do you sort through that..." <- Yeah, when possible, it's usually worth checking the schematics to see. Different docs tend to use different conventions
<Lumpio[m]> There's also "board support packages" or BSPs available for some boards that define names for the pins and have predefined configuration for some onboard peripherals
ni has quit [Remote host closed the connection]
ni has joined #rust-embedded
<AdamHott[m]> Thanks Lumpio and James Munns! Earlier there was a call for blog posts, I wrote this up on github, wondering if anyone would care to review? https://github.com/CodingInGreen/microbit_v2_red_led
spinfast[m] has quit [Quit: Idle timeout reached: 172800s]
dirbaio[m] has quit [Quit: Idle timeout reached: 172800s]
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #rust-embedded
chxry[m] has joined #rust-embedded
<chxry[m]> Is it possible to use defmt-serial and usbd-serial together?
crabbedhaloablut has quit []
notgull has quit [Ping timeout: 264 seconds]
notgull has joined #rust-embedded
StephenD[m] has joined #rust-embedded
<StephenD[m]> dfu on windows is impossible. I guess I will only support linux
sourcebox[m] has joined #rust-embedded
<sourcebox[m]> <StephenD[m]> "dfu on windows is impossible..." <- What are you trying to do? I've written a tool that allows to flash via DFU on Windows. https://github.com/sourcebox/dfu-buddy
<sourcebox[m]> But yes, Windows needs to have the drivers from ST installed.
<StephenD[m]> I'm using the libusb driver, and it shows up now but writing to it causes a libusb access error
<StephenD[m]> Should I just bite the bullet and get the ST drivers?
<sourcebox[m]> StephenD[m]: What tools are you using?
<sourcebox[m]> dfu-util?
<StephenD[m]> Sorry, power just went out. Super stormy here
<StephenD[m]> I will get back to you later though!
<sourcebox[m]> Will not be here anymore because it's already after midnight here.
IlPalazzo-ojiisa has quit [Quit: Leaving.]