When updating v2 Mariko Samsung eMMC from 2.70 to 2.72, the error message "== CLK is not connected" occurs, and I am unable to update the firmware. It remains at version 2.70.
woops, I completely missed the reply. In regards of the sarcasm stuff I'm not used to the notifications of GBATemp and I missinterpreted that comment as a reply to my direct comment, my bad I'm still learning my "foruming".
As for the lenght, I agree. I can try to make them a little more flush on the board. I'll definitely take that advice
As for shorts, I usually run continuity mode to the next-most points to confirm if they're shorting or not, but I couldn't pinpoint anything at the moment I performed the check... maybe it happend after I closed it if at all?
In regards to the mosfet I think that's due to the angle I took the photo. They're actually not touching, let me post another picture rq.View attachment 372279
Its okay.Is 0.1mm wire good for SDA/SCL or should I do it thicker?
Instantly cloned the two repositories, just in case
Already compiled it, and success generated the uf2, but still not yet test it on real device.Instantly cloned the two repositories, just in case
Here's a classicanyone have examples of single mosfet installation photos on lite v2 or oled ?, im so used to using double mosfet
oh, please download files againWhen updating v2 Mariko Samsung eMMC from 2.70 to 2.72, the error message "== CLK is not connected" occurs, and I am unable to update the firmware. It remains at version 2.70.
usk is "no_flash", so you have to use prepare.py to make a complete .uf2Already compiled it, and success generated the uf2, but still not yet test it on real device.
I don't know the purposes of busk, only compile usk.
My pico FW is 2.72. How can I fix it?What version of the fw are you using on Pico. It looks like 2.72 might have an issue with samsung emmc on Oled
I read in the readme in busk. Do we need to modify the memmap_default.ld in the pico_sdk according to that address?usk is "no_flash", so you have to use prepare.py to make a complete .uf2
until that the firmware is RAM only
yesI try to copy pins.h from usk, and the compilation succeed. Is it the same file?
yes, + update.binThis is the uf2 that we usually copy, isn'it?
I think it would work without such modifications. I do that just in case since in a boot process the main firmware overwrites interrupt vector tableI read in the readme in busk. Do we need to modify the memmap_default.ld in the pico_sdk according to that address?
I successfully updated to version 2.72 using the new update.bin Thank you!oh, please download files again
Post automatically merged:
usk is "no_flash", so you have to use prepare.py to make a complete .uf2
until that the firmware is RAM only
download the firmware again, there was a mistake yesterdayWhat is the problem with my Switch OLED?