But the chip looks cool in white imhoIMO, this is just another revision of hwfly and nothing new: same fpga, same mcu, just different PCB to decrease cost and gain a little more profit. So it is not related to any pico here.
But the chip looks cool in white imhoIMO, this is just another revision of hwfly and nothing new: same fpga, same mcu, just different PCB to decrease cost and gain a little more profit. So it is not related to any pico here.
Yeah, I think it's just a "minor" upgrade but using the same mcu and schematic with previous version.
But the chip looks cool in white imho
yeah, you have to love their braveness:IMO, this is just another revision of hwfly and nothing new: same fpga, same mcu, just different PCB to decrease cost and gain a little more profit. So it is not related to any pico here.
Upgradable, as listed on page, so it might be a "hwfly store" but is it actually them making it? or someone else using the brand nameyeah, you have to love their braveness:
View attachment 359459
is a totally changed hwfly, could be you latter couldn't even upgrade it to another firmware nor boot any payload they don't want you to load.
Spider point memeUpgradable, as listed on page, so it might be a "hwfly store" but is it actually them making it? or someone else using the brand name
how to convert file from uf2 to bin ???View attachment 359435
has anyone analyzed this part with ghidra? the static id could be here in two byte pairs
Don't you convert the bin to uf2? Since uf2 is more open?how to convert file from uf2 to bin ???
Use picotool to load to rp2040 as uf2 and then save it to your pc as binhow to convert file from uf2 to bin ???
0x69 noicehowever it is possible to rewrite the firmware, we need to figure out how to write to emmc but it should be similar to sd, then we have the payload and the bct
https://raw.githubusercontent.com/hwfly-nx/firmware/master/firmware/src/payload.h
https://raw.githubusercontent.com/hwfly-nx/firmware/master/firmware/src/mariko_bct.h
Post automatically merged:
payload is sdloader
Bin is a image of the flash, uf2 is the program section data of the chip.how to convert file from uf2 to bin ???
however it is possible to rewrite the firmware, we need to figure out how to write to emmc but it should be similar to sd, then we have the payload and the bct
No offense but this has been probably talked about 20 times by nowhowever it is possible to rewrite the firmware, we need to figure out how to write to emmc but it should be similar to sd, then we have the payload and the bct
https://raw.githubusercontent.com/hwfly-nx/firmware/master/firmware/src/payload.h
https://raw.githubusercontent.com/hwfly-nx/firmware/master/firmware/src/mariko_bct.h
Post automatically merged:
payload is sdloader
Probably because it gets lost in the sea of "how do I install this" or "look at the stuff I bought for when it works"No offense but this has been probably talked about 20 times by now
Asking his progress might help ?View attachment 359435
has anyone analyzed this part with ghidra? the static id could be here in two byte pairs
Probably because it gets lost in the sea of "how do I install this" or "look at the stuff I bought for when it works"
Anyways, if I have this correct, we have 2 uf2's, one from the actual picofly that doesn't boot due to the ID being unique to the pico, and one that boots, but only non-hos payloads?
For anyone that's looked at this in ghidra, have we found the section where the pio is? That's going to most likely be the main communication, since it would effectively allow the pico to bitbang upwards of 100mhz+. I've more or less emulated the gameboy's APU on a pico with heavy pio usage for the audio output. I wouldn't say I'm a pro, but I know how to work with it to an extent.
Lastly, is there any documentation on how this works on the switch side? even if it's at a high level?
But there are rumors that there is a private build of the firmware which can boot atmosphereThere is nothing that can be expected from something that can't even start hos before atmo.