This would be most helpful, I don't know why I didn't think of that earlier.I can provide a full dump of the Meraki firmware for you (or anyone else) to find a remote code execution
This would be most helpful, I don't know why I didn't think of that earlier.I can provide a full dump of the Meraki firmware for you (or anyone else) to find a remote code execution
I PM'd you a link to download the dump.This would be most helpful, I don't know why I didn't think of that earlier.
Does anyone know the wiring to connect my soic16 chip to my ch341a adapter without a soic16 chip clip.
CH341A | MX25L12845E | |
---|---|---|
1 | 16 | Clk |
2 | 7 | CS |
3 | 15 | MOSI / SIn |
4 | 8 | MISO / SOut |
5 | 10 | Ground |
6 | 2 | 3,3V |
7 | do not connect | 5V |
The same here, everything works, but the ports LEDs stay dark.Anybody here with an MS220-8P flashed with this firmware that has working port status lights?
Mine works absolutely fine (ssh, switching and all), except none of the port status lights seem to work.
Just wondering if this is normal.
Hi, I have updated the installation documentation to include the wiring for the SOIC16 chip clip, but it should be pretty easy to see which pins you need to solder to directly. Look for the section titled "SOIC clip wiring" and let me know if it makes sense.Does anyone know the wiring to connect my soic16 chip to my ch341a adapter without a soic16 chip clip.
I have already soldered the wires onto the board before realizing that I do not know where each wire plugs into the ch341a. I looked at the wiring diagram and it did not have several things that my board calls out.
Yes, the port LEDs are non-functional, I'm not sure how to control them. You can check by looking at the port table in /click/switch_port_table/dump_pports (or using switch_status)Anybody here with an MS220-8P flashed with this firmware that has working port status lights?
Mine works absolutely fine (ssh, switching and all), except none of the port status lights seem to work.
Just wondering if this is normal.
I would support this idea, but it has some drawbacks:I'm wondering if the OP would like to sell already flashed chips via paypal for those who can't flash something, but have a hot air station.
There are detailed installation instructions for each model in the MS220 family. If you feel the instructions do not communicate enough detail, you can leave a comment or send me a DM with larger suggestions which I will integrate.I've registered for the forums here specifically because I've just obtained an MS320-48LP with no license and am very interested in testing this out - I'd like it to not remain a paperweight.
Where do I get started with this? I'm not US-based and would need to know what to start looking for and where at local suppliers. Is there an easy-to-follow guide to the flashing process? I'm not a developer, so my interests are purely in having a usable L3 switch at the end of it, but if I can help in the process then that's great![]()
There is progress on having mainline Linux support for the luton26, however thus far I haven't been able to successfully boot a mainline kernel with u-boot.This thread really needs update. waiting for response from the OP.
Installation instructions are herehi good morning.
i have this switch and im interested in change the cisco firmware, please send me the files to unikuerno2004@gmail.com
many thanks.
No guide exists, you must be comfortable using the command line as no management UI exists yet. The firmware is not based on OpenWrt, OpenWrt support requires that the platform is supported by mainline Linux, which is not the case for the vcoreiii used in the MS220 series.Is there a guide on how to use the firmware after installation? What is PostmerkOS exactly? Does it use OpenWrt?
There are guides on how to use the Raspberry Pi as an SPI flasher, e.g. How to flash bios chips with Raspberry Pi - #Tom's WeblogI am trying to flash a MS42P-HW with a raspberry pi 4. How do I connect the pins to the raspberry and how do I set it up to flash the code?
Thanks for the help!No guide exists, you must be comfortable using the command line as no management UI exists yet. The firmware is not based on OpenWrt, OpenWrt support requires that the platform is supported by mainline Linux, which is not the case for the vcoreiii used in the MS220 series.