Hey guys, all new boards have the same MAC address: 00:0a:35:00:01:22. Thus, connection/Ethernet communication to board wont work. Plus Max clock rate is 1000Hz. (sysClockRate) Best regards, Jakub Cmiral
Dear colleagues, On Wednesday 13 of December 2017 20:15:08 Jakub Cmiral wrote:
all new boards have the same MAC address: 00:0a:35:00:01:22. Thus, connection/Ethernet communication to board wont work.
That is strange. If SD cards have been left intact from APO course then each board has an individual address assigned. It is possible that one reserve board can have the address unchanged. At least these addresses should be seen during boot when U-boot obtains DHCP and runs TFTP to load an operating system image. I have no clue how VxWorks obtains an address after startup. Best regards, Pavel Pisa
On Wed, Dec 13 2017, Pavel Pisa wrote:
Dear colleagues,
On Wednesday 13 of December 2017 20:15:08 Jakub Cmiral wrote:
all new boards have the same MAC address: 00:0a:35:00:01:22. Thus, connection/Ethernet communication to board wont work.
That is strange.
No, this is not strange. We forgot to pass the MAC address from the bootloader to the vxWorks driver. We're working on the fix. -MS
On Thu, Dec 14 2017, Michal Sojka wrote:
On Wed, Dec 13 2017, Pavel Pisa wrote:
Dear colleagues,
On Wednesday 13 of December 2017 20:15:08 Jakub Cmiral wrote:
all new boards have the same MAC address: 00:0a:35:00:01:22. Thus, connection/Ethernet communication to board wont work.
That is strange.
No, this is not strange. We forgot to pass the MAC address from the bootloader to the vxWorks driver. We're working on the fix.
The problem with MAC addresses should be fixed now. It would be great if somebody can test it in KN:E-2 lab and report the result here. Thanks. -Michal Sojka
Hello, the problem persists at least at some boards. Used commands and corresponding outputs: -> sysClkRateSet(1001) value = -1 = 0xffffffff -> sysClkRateSet(1000) value = 0 = 0x0 Best regards, Vít Krátký Quoting Michal Sojka <michal.sojka@cvut.cz>:
On Wed, Dec 13 2017, Jakub Cmiral wrote:
Plus Max clock rate is 1000Hz. (sysClockRate)
We have increased max clock rate to 5 kHz. Please somebody check, whether it works.
Best regards, -Michal Sojka
_______________________________________________ PSR mailing list PSR@rtime.felk.cvut.cz You can unsubscribe from the list at https://rtime.felk.cvut.cz/mailman/listinfo/psr
On Thu, Dec 21 2017, Vít Krátký wrote:
Hello,
the problem persists at least at some boards.
Used commands and corresponding outputs: -> sysClkRateSet(1001) value = -1 = 0xffffffff -> sysClkRateSet(1000) value = 0 = 0x0
You are right. Now it's really fixed and tested as well. The problem was that maximum clock rate can be set at two places: BSP and kernel configuration. Previously we set it in BSP, but kernel configuration overrides the BSP value. Best regards, -Michal Sojka
participants (4)
-
Jakub Cmiral -
Michal Sojka -
Pavel Pisa -
Vít Krátký