Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision | ||
| inbox:toh:cisco:vedge_1000 [2024/03/17 08:24] – [Serial] bluecmd | inbox:toh:cisco:vedge_1000 [2024/08/11 12:20] – [Installing OpenWrt] bluecmd | ||
|---|---|---|---|
| Line 17: | Line 17: | ||
| Basic plattform support is available in the main branch since https:// | Basic plattform support is available in the main branch since https:// | ||
| - | Currently there is a private fully-featured | + | Currently there is a [[https:// |
| ===== Supporting activities ===== | ===== Supporting activities ===== | ||
| Line 30: | Line 30: | ||
| ===== Experimental firmware ===== | ===== Experimental firmware ===== | ||
| - | None at this time. | + | See https:// |
| /*** | /*** | ||
| * External image (add link) | * External image (add link) | ||
| Line 43: | Line 44: | ||
| + | USB per-port power switching (PPPS) is available for both USB 3 front ports. | ||
| /*** if info available: uncomment and fill in | /*** if info available: uncomment and fill in | ||
| Line 49: | Line 51: | ||
| - → [[docs: | - → [[docs: | ||
| - → [[: | - → [[: | ||
| + | ***/ | ||
| ==== Installing OpenWrt ==== | ==== Installing OpenWrt ==== | ||
| - | ***/ | ||
| + | === Alternative 1: Boot installation from unlocked u-boot via TFTP === | ||
| + | |||
| + | * Download the '' | ||
| + | * Example TFTP server command to serve the files in the current directory: '' | ||
| + | * Calculate the CRC32 of your boot file using the following command: < | ||
| + | |||
| + | * If you are not in the u-boot prompt, reboot the device and press **Ctrl-x** to enter u-boot | ||
| + | * If this does not work, see the " | ||
| + | * Connect the vEdge 1000 via the management Ethernet port to a network with DHCP available | ||
| + | * Run the following commands, replace the IP with your TFTP server: | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * If the previous crc32 command does not complain, continue with the boot | ||
| + | * '' | ||
| + | * Continue with the **Prepare the disk** step | ||
| + | |||
| + | === Alternative 2: Boot installation from inside OEM OS (USB drive, SD card, SSH, HTTP(S)) === | ||
| + | |||
| + | **Note:** OEM OS only supports mounting vfat partitions automatically | ||
| + | |||
| + | * Copy '' | ||
| + | * '' | ||
| + | * Reboot vEdge | ||
| + | * Press ctrl-x to enter u-boot | ||
| + | * Run the following commands: | ||
| + | * '' | ||
| + | * '' | ||
| + | * '' | ||
| + | * Continue with the **Prepare the disk** step | ||
| + | |||
| + | === Prepare the disk === | ||
| + | The vEdge 1000 has been found to have a disk ID of zero by default. This needs to be rectified in order for OpenWrt to reliably be able to find the root partition. This step only has to be done once as it is permanent unless the full disk is re-partitioned manually by the user. | ||
| + | |||
| + | * Verify if you need to change the disk ID by running '' | ||
| + | * You should get a single line like this: ''/ | ||
| + | * If you are missing the '' | ||
| + | * Generate a new disk ID by running the following commands: | ||
| + | * < | ||
| + | source / | ||
| + | sfdisk --disk-id " | ||
| + | </ | ||
| + | * Now loop back to step 1 above and verify that the boot partition has a '' | ||
| + | |||
| + | === Running the installation === | ||
| + | |||
| + | You need to make the file '' | ||
| + | |||
| + | **Example using OpenSSH:** | ||
| + | |||
| + | < | ||
| + | udhcpc -i br-lan | ||
| + | # On another machine: scp -O openwrt-octeon-generic-cisco_vedge1000-squashfs-sysupgrade.tar root@10.x.x.x:/ | ||
| + | sysupgrade -n / | ||
| + | </ | ||
| + | |||
| + | **Example using a USB drive:** | ||
| + | |||
| + | < | ||
| + | mount /dev/sdb1 /mnt | ||
| + | sysupgrade -n / | ||
| + | </ | ||
| + | |||
| + | Done! It is recommended to power-cycle the device to ensure that e.g. the LED and USB controllers are reset to a known state. | ||
| + | |||
| + | === Sync and reset fallback partitions === | ||
| + | |||
| + | The vEdge 1000 has support for two U-Boot bootloaders. It is recommended to sync and force a switch to the primary partition. | ||
| + | |||
| + | In U-Boot, execute the following: | ||
| + | |||
| + | < | ||
| + | # optional: ensure USB3 ports are enabled | ||
| + | setenv ext_usb_setup "i2c dev 1; i2c smbwrite 6e 01 01 ff; cpld_wr 0x4 0x00" | ||
| + | |||
| + | cpld_wr 0xa 0x2 | ||
| + | saveenv | ||
| + | cpld_wr 0xa 0x0 | ||
| + | saveenv | ||
| + | reset | ||
| + | </ | ||
| + | ==== Reverting back to OEM ==== | ||
| + | |||
| + | < | ||
| + | source / | ||
| + | mkdir /mnt | ||
| + | mount " | ||
| + | rm / | ||
| + | umount /mnt | ||
| + | reboot | ||
| + | </ | ||
| + | |||
| + | In the " | ||
| + | The system will restart but fail to boot with a bunch of file system related errors. At this point press the reset button on the front panel for 10 seconds and let go. | ||
| + | The system should now boot up correctly in the OEM software | ||
| ===== Debricking ===== | ===== Debricking ===== | ||
| Line 153: | Line 250: | ||
| ***/ | ***/ | ||
| - | The unit is shipped with two power adapters, part number FSP060-DIBAN2. A DC connector w/ the dimensions 2.1×5.5×9.5mm is suitable. | + | The unit is shipped with two power adapters, part number FSP060-DIBAN2. A DC connector w/ the dimensions 2.1×5.5×9.5mm is suitable. The stock PSU is rated 60W but in reality anything at 30W or higher should work fine. During stress testing the vEdge 1000 has been pushed to draw 28W at worst-case but during normal loads it should be closer to 15-20W. The unit works fine with voltage levels between 6.5V up to 15.2V - higher voltages might be possible but has not been tested. |
| Line 218: | Line 315: | ||
| <WRAP BOX> | <WRAP BOX> | ||
| The serial interface on the front is a standard Cisco RJ45 serial port labelled as " | The serial interface on the front is a standard Cisco RJ45 serial port labelled as " | ||
| - | On newer firmwares this method is not directly accessible and might require additional work. | + | On newer firmwares this method is not directly accessible and will require additional work, see below. |
| Alternatively the USB Type-B on the front can be used to connect to the serial console. | Alternatively the USB Type-B on the front can be used to connect to the serial console. | ||
| Line 272: | Line 369: | ||
| The least complicated way to unlock U-boot is to create a file called '' | The least complicated way to unlock U-boot is to create a file called '' | ||
| - | |||
| - | |||
| - | {{ media: | ||
| As part of the secure boot flow U-boot will be searching for an I2C EEPROM at address 0x75 on the JP3 header (see " | As part of the secure boot flow U-boot will be searching for an I2C EEPROM at address 0x75 on the JP3 header (see " | ||
| One straightforward way to create such a gadget is to use an Arduino microcontroller. Documented below is code and connection schematic for using an Arduino Uno controller connected via normal 0.64mm jumper wire. If you have no previous experience nor equipment to build this hardware yourself there are kits available that contain everything you need - example of such a kit is the [[https:// | One straightforward way to create such a gadget is to use an Arduino microcontroller. Documented below is code and connection schematic for using an Arduino Uno controller connected via normal 0.64mm jumper wire. If you have no previous experience nor equipment to build this hardware yourself there are kits available that contain everything you need - example of such a kit is the [[https:// | ||
| + | |||
| + | {{ media: | ||
| Use the following code: | Use the following code: | ||
| Line 873: | Line 969: | ||
| ===== Notes ===== | ===== Notes ===== | ||
| + | ==== USB power switching ==== | ||
| + | |||
| + | To power down the top port you can do: | ||
| + | |||
| + | < | ||
| + | echo 1 > / | ||
| + | echo 1 > / | ||
| + | </ | ||
| + | |||
| + | For the bottom port use '' | ||
| + | |||
| + | The software uhubctl can be used, but as of this writing there are some issues regarding endianness and devices hanging around in the kernel even when being powered down. | ||
| + | |||
| + | ==== Gotchas ==== | ||
| + | |||
| + | === Trying to up an interface fails === | ||
| + | |||
| + | < | ||
| + | root@OpenWrt:/# | ||
| + | RTNETLINK answers: No error information | ||
| + | </ | ||
| + | |||
| + | This will happen if the port is configured for SGMII and did not have a PHY inserted at boot time. Reboot the unit and it should be able to up the link. | ||
| + | |||
| + | === Kernel panic - not syncing: ������ === | ||
| + | |||
| + | This message with broken glyphs can occur if you enable CONFIG_TARGET_INITRAMFS_COMPRESSION. Maybe the support is broken for MIPS64, or maybe it is broken for just this platform. | ||
| + | |||
| + | === Crash when loading kernel after " | ||
| + | |||
| + | This error can happen if the initramfs image is too large. Images larger than 256 MiB seems to be unbootable. | ||
| + | |||
| + | Example log: | ||
| + | |||
| + | < | ||
| + | Bytes transferred = 432629896 (19c96888 hex) | ||
| + | => bootoctlinux $loadaddr endbootargs | ||
| + | argv[2]: endbootargs | ||
| + | Allocating memory for ELF segment: addr: 0xffffffff81100000 (adjusted to: 0x1100000), size 0x19ea1360 | ||
| + | |||
| + | Reg: 0x0 0x0 | ||
| + | Reg: 0x1 0x0 | ||
| + | Reg: 0x2 0x30000000 | ||
| + | Reg: 0x3 0xD1D2D3D4D5D6D7DC | ||
| + | Reg: 0x4 0x19EA1360 | ||
| + | Reg: 0x5 0xD1D2D3D4D5D6D7DC | ||
| + | Reg: 0x6 0x1100000 | ||
| + | Reg: 0x7 0x8000000000000000 | ||
| + | Reg: 0x8 0x6C108 | ||
| + | Reg: 0x9 0xFFFFFFFFFFFFFFF0 | ||
| + | Reg: 0xA 0x30000000 | ||
| + | Reg: 0xB 0xD1D2D3D4D5D6D7E4 | ||
| + | Reg: 0xC 0xDEDF00000000003C | ||
| + | Reg: 0xD 0xDEDF00003000003C | ||
| + | Reg: 0xE 0x800000000006C110 | ||
| + | Reg: 0xF 0x1 | ||
| + | Reg: 0x10 0x1AFA1360 | ||
| + | Reg: 0x11 0xF | ||
| + | Reg: 0x12 0x0 | ||
| + | Reg: 0x13 0x19EA1360 | ||
| + | Reg: 0x14 0x0 | ||
| + | Reg: 0x15 0x1100000 | ||
| + | Reg: 0x16 0x0 | ||
| + | Reg: 0x17 0x1100000 | ||
| + | Reg: 0x18 0xFFFFFFFFC00F0180 | ||
| + | Reg: 0x19 0xFFFFFFFFC0001BC0 | ||
| + | Reg: 0x1A 0xFFFFFFFFFFFF97F8 | ||
| + | Reg: 0x1B 0xFFFFFFFFFFFF97F8 | ||
| + | Reg: 0x1C 0xFFFFFFFFC00CD3C0 | ||
| + | Reg: 0x1D 0xFFFFFFFFC0FAF7B0 | ||
| + | Reg: 0x1E 0x0 | ||
| + | Reg: 0x1F 0xFFFFFFFFC0001D1C | ||
| + | status: | ||
| + | cause: | ||
| + | epc: 0xFFFFFFFFC0001DEC | ||
| + | badvaddr: | ||
| + | instruction: | ||
| + | |||
| + | stack: | ||
| + | 0xFFFFFFFFC0FAF6B0 : 0xFFFFFFFFC012AB98 0xFFFFFFFFC03A1A88 | ||
| + | 0xFFFFFFFFC0FAF6C0 : 0x5F5F746D705F7265 0x7365727665645F6C | ||
| + | 0xFFFFFFFFC0FAF6D0 : 0x696E757800000000 0x536B697070696E67 | ||
| + | 0xFFFFFFFFC0FAF6E0 : 0x206E6F6E204C4F41 0x442070726F677261 | ||
| + | 0xFFFFFFFFC0FAF6F0 : 0x6D20686561646572 0x2028747970652030 | ||
| + | </ | ||
| ===== Tags ===== | ===== Tags ===== | ||
| {{tag> | {{tag> | ||