Cisco Meraki MX64/MX65 image support

For Developers
67

can I have the MX64 OpenWRT image pleas

68

https://drive.google.com/file/d/1z8Epbpy0MhcwcDvK53FadYD0HlocCn1e/view?usp=sharing

Just be careful mate, follow the instructions from clayface

69

Thank you, bro :heart:

70

Well now I’m having an issue that it’s not booting into OpenWRT via the usb I did the previous steps 5 times and yet it doesn’t boot also I tired multiple USB’s formatted FAT as it was mentioned in claycface’s instructions so I don’t know what’s the problem however I need to run extra commands for the device as it’s mtd0 locked so I don’t know if it’s the image or the device or the usb I don’t know plus when I turn it on while the pin is in the reset hole I get a quick white and oranges flash then it goes orange for a few seconds then rainbow so did I do the process correct because I don’t think it’s mento to go to that stage and when I try to run this command “scp bin/targets/bcm5862x/generic/openwrt-bcm5862x-generic-meraki_mx64-squashfs-sysupgrade.bin 192.168.1.1:/tmp” it says connection refused and the port 22 isn’t open so can someone help me plz. Sorry if this is quite long

71

Try "scp bin/targets/bcm5862x/generic/openwrt-bcm5862x-generic-meraki_mx64-squashfs-sysupgrade.bin root@192.168.1.1:/tmp" instead

72

yeah I have no luck yet so it's the booting into OpenWRT issue because how am I meant to know if I have booted into OpenWRT so I'm kinda lost

73 
C:\Users\rayya\Downloads\MX64>scp openwrt-bcm5862x-generic-meraki_mx64a0-squashfs-sysupgrade.bin root@192.168.1.1:/tmp
ssh: connect to host 192.168.1.1 port 22: Connection aborted

C:\Users\rayya\Downloads\MX64>scp openwrt-bcm5862x-generic-meraki_mx64a0-squashfs-sysupgrade.bin root@192.168.1.1:/tmp
ssh: connect to host 192.168.1.1 port 22: Unknown error
lost connection

this is what I get when I try to run the command

74

Be very careful following the instructions from clayface!

  • The image I've shared with you(regular mx64 release) is ment to be used if the output of "devmem 0x18000000" is "0x3F04" or higher (during U-boot installation).
    Make sure what release you need mx64 or mx64a0

  • What you get when you ping 192.168.1.1?

1 Like
75

yeah mine is "0x3F04" higher than that but when I ping 192.168.1.1 I get my Netgear coming up and when I do nmap on 192.168.1.1 I get this

C:\Users\rayya>nmap 192.168.1.1
Starting Nmap 7.91 ( https://nmap.org ) at 2021-03-25 15:51 GMT Standard Time
Nmap scan report for 192.168.1.1
Host is up (0.0058s latency).
Not shown: 991 closed ports
PORT      STATE    SERVICE
21/tcp    filtered ftp
53/tcp    open     domain
80/tcp    open     http
443/tcp   open     https
631/tcp   open     ipp
2601/tcp  open     zebra
2602/tcp  open     ripd
20005/tcp open     btx
49152/tcp open     unknown
MAC Address: 78:D2:94:B4:FD:4D (Netgear)

Nmap done: 1 IP address (1 host up) scanned in 2.85 seconds

however, I am able to use wget to get the files off my webserver when I telnet into it

btw if you have discord add me if you can so we can talk and solve this pleas

rayboy777#9289

76

Hi there if you don't mind waiting a day or two, I am going to implement crc32 method in firmware tools as it is in uboot. There is potential for issues due to differences in how it has been implemented as well as the possibility of the utility not being available on the build system.

@Rayyan do you have the serial connected to see what's going on? I confirmed the initramfs file in the archive from @zerg91 boots fine. Do you have a read indicator LED on the usb stick to confirm activity?

77

so I have a serial adapter its the USB To RS232 TTL CH340G Converter Module however I don't know which pins they are plus when I try to read the serial connection I get random letters and numbers I tried every baud rate and nothing helped
here is the picture of the adapter https://drive.google.com/file/d/1uy2gj2N2KjhvGg_ho1esGW1TrMGyRkxV/view?usp=sharing
and here is the picture of the board
https://drive.google.com/file/d/1US9FSz3mKaxyxGM6_-SWZsNCKR3wOGi-/view?usp=sharing
also, I'm adding a video of me doing the second step after the telnet process
https://drive.google.com/file/d/1cg6H_h8ma4WkN2XgJM_AzRGp4nuNYKOQ/view?usp=sharing

and yes my USB does have a red indicator

78

The rainbow LED is the meraki fw so at this point it hasn't worked. uboot is installed so that part you don't need to worry, but would really need see what's going on over serial if you can get it to work (115200 8N1 flow control off). The USB is formatted FAT and the initramfs file (not sysupgrade) is there, not renamed? Are the contacts on the port and usb drive clean? It takes several seconds to load from USB so look out for this from the indicator.

79

Check the wiki for the serial pins connections Link is detailed further up in this thread.

80

but on mine, I only have J1 and J3 if you go back to my comment about the serial you should be able to see what I'm talking about that the problem I have which pins are those for

This is what i get See video
https://drive.google.com/file/d/1XISCScabqgz5tbmTuy1nTQM6TXyv6fGW/view?usp=sharing

81

Sorry was a mistake on my part I have now updated the Wiki and added a picture as well

For the MX64:
Set of 4 pins labeled J1

  • Pin 1 - (has a small triangle symbol under it) closest to the main processor (3.3v) DO NOT CONNECT!
  • Pin 2 - connected to RX on my USB adapter
  • Pin 3 - connected to TX on my USB adapter
  • Pin 4 - (closest to the LED) connected to Ground on my USB adapter

Serial connection parameters 115200, 8N1

82

Thank you very much for the compilation.

now i have openWRT on my MX64.

I just couldn't install LuCi or other programs with the opkg commands

83

okay i generally think the default 192.168.1.1 IP for telnet is frozen as when i type ipconfig on cmd this is what i get

Ethernet adapter MX64:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::c817:743d:b619:984d%16
   Autoconfiguration IPv4 Address. . : 169.254.152.77
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . .

and when I add and custom IP like 192.168.1.1 this is what I get

Ethernet adapter MX64:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::c817:743d:b619:984d%16
   IPv4 Address. . . . . . . . . . . : 192.168.1.1
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :

btw its in its recovery mode wheere telnet should work however when i do nmap on the custom ip
i get this and my wifi is off

C:\Users\rayya>nmap 192.168.1.1
Starting Nmap 7.91 ( https://nmap.org ) at 2021-03-26 11:24 GMT Standard Time
Nmap scan report for 192.168.1.1
Host is up (0.00055s latency).
Not shown: 989 closed ports
PORT      STATE SERVICE
135/tcp   open  msrpc
139/tcp   open  netbios-ssn
445/tcp   open  microsoft-ds
554/tcp   open  rtsp
902/tcp   open  iss-realsecure
912/tcp   open  apex-mesh
1088/tcp  open  cplscrambler-al
1095/tcp  open  nicelink
2869/tcp  open  icslap
5357/tcp  open  wsdapi
10243/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 13.96 seconds

and i get the same output for nmap when the defult ip of the MX64 is 169.254.152.77

and i cant accses the serial even tho i follewd @CM65 steps

84

how can you explain because i think mine is bricked

85

so i followed the steps you have given however I get this

image
image1007×581 7.01 KB

86

With output like that it looks like you have a connection just the wrong speed. (but you had it correct in the earlier video)
2 things to try

  • In putty on the main screen select the comm port and set speed to 115200. don't worry about changing any other settings.
  • remove the jumper on your USB TTL device it might be causing issues and i would think the USB device is drawing power from the USB bus anyway