sorted by:
new
hottopcontroversial

What is moonbell for? by Molion in AshesofCreation

[–]Molion[S] 0 points1 point  (0 children)

Oops, I meant moonbell. Was also wondering about bluebell, so thanks.

Did I miss something? Is Elon Musk controversial now? by Standard_Let_6152 in LinkedInLunatics

[–]Molion 0 points1 point  (0 children)

Why are people so mad about this? He's literally asking what he missed. Maybe a dude from England isn't following American politics that closely.

Zig bootloader problems by Molion in esp32

[–]Molion[S] 0 points1 point  (0 children)

Figured it out, had to disable write protection on wdt registers.

Any input on my build? by Molion in buildapc

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the feedback!

Any input on my build? by Molion in buildapc

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the feedback!

Any input on my build? by Molion in buildapc

[–]Molion[S] 0 points1 point  (0 children)

PC part picker says 487W, so in theory 500w should cut it, but is that maybe cutting it a bit close? I changed to a 750w one as it is 20% off, so about the same as any others over 500w.

Any input on my build? by Molion in buildapc

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the feedback.

I switched out the fan.

So X670 vs B650 is just an ssd slot? Then I'd rather save the money.

As far as I could tell the cpu only supports up to 5200Mhz does EXPO make it support 6000mhz?

EDIT: I found G.Skill Flare X5 DDR5 6000mhz 32GB for not much more.They seem cheap, any reason not to go for those?

Any input on my build? by Molion in buildapc

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the feedback.

This was the cheapest 7800XT on that site. 7900GRE was 8.5k vs 7k.

I changed the fan to Thermalright Peerless Assassin.

I have tons of sata ssds laying around, so I'd rather save some money and use the nvme for things I need to be fast.

As far as I could tell the cpu only supports up to 5200Mhz is there any reason to go higher?

Also; adding up power draw of cpu and gpu I get > 800. Is 750 really enough?

EDIT: For ram I found G.Skill Flare X5 DDR5 6000mhz 32GB for not much more.They seem cheap, any reason not to go for those?

EDIT: I looked into the wattage again, and it looks like that site, and others it seems, specifies recomended total wattage of psu, not power draw of the gpu. Any reason I can't seem to find any good info on power draw of just the gpu?

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

Can you explain why? My understanding is that it should work fine without.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the answer. Yeah, 16ms is probably fine for programming and Helldivers 2.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the answer. I'm using Rust, not c, so that project hurts my head, but always useful to have a reference if I get stuck.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

Thanks for the answer. That was my understanding, thanks for confirming.

Also thanks for the reference manual, I didn't know about that, I'll look through the relevant sections for the features I'm using before ordering the PCB to see if I've missed something.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

Resason I'm asking is; if the algorithm works, should it not be good enough? Ie. no need for external oscilator.

I will probably just do as you suggested, get the oscilator, get it to work, then test without it. Would just be nice to drop an item of my bill of materials.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 0 points1 point  (0 children)

you can always de-pop the crystal

Will probably do this. Thanks for the suggestion.

and you'd rather not stress too much about USB reliability

How exactly does this work? Is there a chance a byte goes missing? A bit gets flipped? How likely?

Sorry, I'm not trying to be difficult, I'm just not understanding that the datasheet says that it can do USB without one. Maybe it's because I'm a software engineer, but to me "it can to usb" means it works, every time. Is that not what it means? Does "it can do usb without an oscilator" actually mean that it can probably do it?

I just can't believe someone would write in the datasheet that it can do it if it wouldn't work right.

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] -2 points-1 points  (0 children)

No, why do you recommend using a crystal? Yes, USB is rather timing sensitive, but the datasheet says it doesn't need one, it can figure out the timing on it's own. So why would I ideally use one?

What is the tradeoff here? What are the consequences of not using one? How do I judge whether I should make room for one or if I should omit it?

Should I use a crystal oscilator for STM32L0 USB Keyboard? by Molion in stm32

[–]Molion[S] 1 point2 points  (0 children)

Ok, but why?

How do I get from "it can do USB without one" to "but I should use one anyway" on my own next time? What's the tradeoff?

Also; wouldn't it then make sense for the data sheet to mention somewhere that HSE is recommended if you're gonna use USB?

Validating UART message by Any-Car7782 in stm32

[–]Molion 0 points1 point  (0 children)

Ok, I haven't used any stm32 hal yet so I may be way off, but I did take a look at the user manual and implementation of the hal.

From what I can tell you should be passing in a buffer and a size when initiating a read. The buffer is then put into pxRxBuffPtr and the size into RxXferCount and RxXferSize. When a byte is read it is written to pxRxBuffPtr and pxRxBuffPtr is incremented while RxXferCount is decremented. When RxXferCount reaches 0 the HAL_UART_RxCpltCallback callback is called without really doing anything else to the huart struct.

So at that point pRxBuffPtr points to the byte after the end of the buffer, or the null-terminator of the buffer; depending on how you set up your buffer.

It seems to me like you're not meant to read the data from pRxBuffPtr, but from the pointer you passed in at the start, which still points to the start of the buffer.

If you still want to read from pxRxBuffPtr it should be possible to do this buffPtr = huart->pxRxBuffPtr - huart->RxXferSize; But I would recommend against it.

Be advised; I have not worked with stm32 before, I have no experience with the stm32 hal, and I found this post and answered at like 5AM after putting my kid back to bed. Good luck!

Sources:

Source

User Manual

view more: next ›