Skip to content

Updated hs lab devices#176

Merged
aparcar merged 6 commits into
aparcar:mainfrom
bryansancheZ199:main
Sep 29, 2025
Merged

Updated hs lab devices#176
aparcar merged 6 commits into
aparcar:mainfrom
bryansancheZ199:main

Conversation

@bryansancheZ199

Copy link
Copy Markdown
Contributor

No description provided.

@aparcar

aparcar commented Sep 11, 2025

Copy link
Copy Markdown
Owner

please fix the commit subjects, they should contain a "tag" and then a description of what happened, not just "new device", but "devices: add foo bar xyzzy"

Also your test setup seems incomplete, the DUT is not downloading the image

CONSOLE SerialLogger.ma:    SerialDriver(main) < ␍ NetLoop,call eth_init ! ␤␍Trying Eth0 (10/100-M)␤␍␤
CONSOLE SerialLogger.ma:    SerialDriver(main) < ␍ Waitting for RX_DMA_BUSY status Start... done␤␍␤
CONSOLE SerialLogger.ma:    SerialDriver(main) < ␍␤
CONSOLE SerialLogger.ma:    SerialDriver(main) < ␍ ETH_STATE_ACTIVE!! ␤␍TFTP from server 192.168.1.2; our IP address is 192.168.1.1␤␍Filename 'glinet_gl-mt1300//openwrt-24.10.2-ramips-mt7621-glinet_gl-mt1300-initramfs-kernel.bin'.␤␍␤
CONSOLE SerialLogger.ma:    SerialDriver(main) < ␍ TIMEOUT_COUNT=10,Load address: 0x81000000␤␍Loading: *␈T T T ␍␤```

@bryansancheZ199

Copy link
Copy Markdown
Contributor Author

Fixed problem on glinet_gl-mt1300, the ethernet ports were disconnected, please check again. For next commit I will add more description on the changes made it.

@aparcar

aparcar commented Sep 11, 2025

Copy link
Copy Markdown
Owner

Still timeout

@bryansancheZ199

Copy link
Copy Markdown
Contributor Author

For the device glinet_gl-mt1300 I am fixing the ip address to have comunication with the tftp server and to tell it to run the boot file. And for the [linksys_e8450] do not test it, it is just connected via serial but not ethernet due to we dont have any more ports available (the new switch haven't arrive yet).

@jonasjelonek

Copy link
Copy Markdown
Collaborator

This looks to me like it doesn't work because the IP of the TFTP provided by the controller and the hardcoded one in the U-boot env do not match. I'd propose to change it in the bootloader instead of changing the network setup.

@aparcar should this be changed once manually now in the U-boot env or can we do that dynamically via labgrid, e.g. as part of the init_commands?

bryansancheZ199 and others added 2 commits September 23, 2025 17:46
…t not tested device tplink_tl-wr1043nd-v4, device glinet_gl-mt1300 still not proper configured and added but not tested device linksys_e8450.
This device is already connected to the system but untested
@aparcar aparcar merged commit 6d0427a into aparcar:main Sep 29, 2025
14 of 18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants