VS无法设置默认的Code Page（encoding）？

asp.net mvc

AspNetMVC2_RC_VS2008.exe ASP.NET MVC 2 Release Candidate Release Notes This document describes the Release Candidate release of the ASP.NET MVC 2 framework. Installation Notes 2 Documentation 2 Support 2 Upgrading an ASP.NET MVC 1.0 Project to ASP.NET MVC 2 2 New Features 3 ASP.NET MVC validation scripts have been moved to their own file 4 ASP.NET MVC validation scripts can be included at the top or bottom of a page 4 ASP.NET MVC validation scripts support globalization 4 Html.ValidationSummary helper method can display model-level errors 4 T4 templates in Visual Studio generate code that is specific to the target version of the .NET Framework 4 Other Improvements 4 Bug Fixes 5 Breaking Changes 5 Changes in ASP.NET MVC 2 Release Candidate 5 Changes in ASP.NET MVC 2 Beta 6 Changes in ASP.NET MVC 2 Preview 2 6 Changes in ASP.NET MVC 2 Preview 1 7 Known Issues 7 Disclaimer 8 This document describes the Release Candidate release of ASP.NET MVC 2 for Visual Studio 2008 SP1. Installation Notes The ASP.NET MVC 2 Release Candidate for Visual Studio 2008 SP1 can be downloaded from the following page: http://go.microsoft.com/fwlink/?LinkID=157071 ASP.NET MVC 2 can be installed and can run side-by-side with ASP.NET MVC 1.0. Note   Because Visual Studio 2008 and Visual Studio 2010 Beta 2 share a component of ASP.NET MVC 2, installing the ASP.NET MVC 2 Release Candidate release on a computer where Visual Studio 2010 Beta 2 is also installed is not supported. Documentation Documentation for ASP.NET MVC 2, which includes tutorials, technology overviews, code samples, and API reference, is available on the MSDN Web site. A good starting point is the ASP.NET Model View Controller (MVC) topic (http://go.microsoft.com/fwlink/?LinkId=159758). Tutorials and other information about ASP.NET MVC are also available on the ASP.NET Web site (http://www.asp.net/mvc/). Support This is a Release Candidate (RC) release and is not officially supported. If you have questions about working with this release, post them to the ASP.NET MVC forum (http://forums.asp.net/1146.aspx), where members of the ASP.NET community are frequently able to provide informal support. Upgrading an ASP.NET MVC 1.0 Project to ASP.NET MVC 2 To upgrade an existing ASP.NET MVC 1.0 application to version 2, follow these steps: Make a backup of the existing project. Open the project file in a text editor (the file with the .csproj or .vbproj file extension) and find the ProjectTypeGuid element. As the value of that element, replace the GUID {603c0e0b-db56-11dc-be95-000d561079b0} with {F85E285D-A4E0-4152-9332-AB1D724D3325}. When you are done, the value of that element should be as follows: <ProjectTypeGuids>{F85E285D-A4E0-4152-9332-AB1D724D3325};{349c5851-65df-11da-9384-00065b846f21};{fae04ec0-301f-11d3-bf4b-00c04f79efbc}</ProjectTypeGuids> In the Web application root folder, edit the Web.config file. Search for System.Web.Mvc, Version=1.0.0.0 and replace all instances with System.Web.Mvc, Version=2.0.0.0. Repeat the previous step for the Web.config file located in the Views directory. Open the project using Visual Studio, and in Solution Explorer, expand the References node. Delete the reference to System.Web.Mvc (which points to the version 1.0 assembly). Add a reference to System.Web.Mvc (v2.0.0.0). Add the following bindingRedirect element to the Web.config file in the application root under the configuraton section: <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35"/> <bindingRedirect oldVersion="1.0.0.0" newVersion="2.0.0.0"/> </dependentAssembly> </assemblyBinding> </runtime> Create a new ASP.NET MVC 2 application. Copy the files from the Scripts directory of the new application into the Scripts directory of the existing application. Compile the application and run it. If any errors occur, refer to the Breaking Changes section of this document for possible solutions. New Features This section describes features that have been introduced in the ASP.NET MVC 2 Release Candidate release. ASP.NET MVC validation scripts have been moved to their own file To help reduce conflicts with other Ajax libraries, the built-in ASP.NET MVC validation scripts are now in a separate JavaScript file. ASP.NET MVC validation scripts can be included at the top or bottom of a page The server component that renders the client validation metadata now renders the metadata into a JavaScript variable. This allows the validation scripts to be included either at the top of the page or at the bottom, because the scripts will look for the variable and load the metadata when it is available. ASP.NET MVC validation scripts support globalization When the required ASP.NET Ajax globalization scripts are included in a page, the validation logic uses the culture-specific data for data types (such as dates and numbers) when it validates input text. The new Html.GlobalizationScript helper method can be used to render a reference to the globalization script for the current culture. Html.ValidationSummary helper method can display model-level errors Instead of always displaying all validation errors, the Html.ValidationSummary helper method has a new option to display only model-level errors. This enables model-level errors to be displayed in the validation summary and field-specific errors next to each field. T4 templates in Visual Studio generate code that is specific to the target version of the .NET Framework A new property is available to T4 files from the ASP.NET MVC T4 host that specifies the version of the .NET Framework that is used by the application. This allows T4 templates to generate code and markup that is specific to a version of the .NET Framework. In Visual Studio 2008, the value is always .NET 3.5. In Visual Studio 2010, the value is either .NET 3.5 or .NET 4. Other Improvements The following additional changes have been made to existing types and members for the ASP.NET MVC 2 Release Candidate release. The default HTML markup that is generated by the Add View dialog box has been changed to be consistent with the markup that is rendered by the templated helpers (Editor, EditorFor, Display, and DisplayFor). Buttons in a form can specify that they do not cause validation logic to run. The default is that every button in a form causes validation logic to run, and if validation fails, the validation logic blocks submission of the form. Enabling validation selectively for buttons lets you create forms that can post information even if a form is not complete or if the form contains data that is temporarily invalid. Client validators can specify when they run. Possible values are input (while the user is typing), blur (after the user is done typing and moves to another field), and submit (when the user submits the form). Bug Fixes The following bugs have been fixed in the ASP.NET MVC 2 Release Candidate release. The FileResult action result now supports non-US-ASCII characters in file names. Methods and properties of the TempDataDictionary class have been improved to better handle the case when items are flagged for removal from the dictionary. Support for validation in the IDataErrorInfo interface has been fixed. Breaking Changes The following changes might cause errors in existing ASP.NET MVC 1.0 applications. Changes in ASP.NET MVC 2 Release Candidate IIS script mapping script is no longer available in the installer The IIS script mapping script is a command-line script that is used to configure script maps for IIS 6 and for IIS 7 in Classic mode. The script-mapping script is not needed if you use the Visual Studio Development Server or if you use IIS 7 in Integrated mode. The scripts are available as a separate unsupported download on the ASP.NET CodePlex site. The Html.Substitute helper method in MVC Futures is no longer available Due to changes in the rendering behavior of MVC view engines, the Html.Substitute helper method does not work and has been removed. Changes in ASP.NET MVC 2 Beta The IValueProvider interface replaces all uses of IDictionary<string, ValueProviderResult> Every property or method argument that accepted IDictionary<string, ValueProviderResult> now accepts IValueProvider. This change affects only applications that include custom value providers or custom model binders. Examples of properties and methods that are affected by this change include the following: The ValueProvider property of the ControllerBase and ModelBindingContext classes. The TryUpdateModel methods of the Controller class. New CSS classes were added in the Site.css file that are used to style validation messages. Changes in ASP.NET MVC 2 Preview 2 Helpers now return an MvcHtmlString object In order to take advantage of the new HTML-encoding expression syntax in ASP.NET 4, the return type for HTML helpers is now MvcHtmlString instead of a string. Note that if you use ASP.NET MVC 2 and the new helpers with ASP.NET 3.5, you will not be able to take advantage of the HTML-encoding syntax; the new syntax is available only when you run ASP.NET MVC 2 on ASP.NET 4. JsonResult now responds only to HTTP POST requests In order to mitigate JSON hijacking attacks that have the potential for information disclosure, by default, the JsonResult class now responds only to HTTP POST requests. Ajax GET calls to action methods that return a JsonResult object should be changed to use POST instead. If necessary, you can override this behavior by setting the new JsonRequestBehavior property of JsonResult. For more information about the potential exploit, see the blog post JSON Hijacking on Phil Haack’s blog. Model and ModelType property setters on ModelBindingContext are obsolete A new settable ModelMetadata property has been added to the ModelBindingContext class. The new property encapsulates both the Model and the ModelType properties. Although the Model and ModelType properties are obsolete, for backward compatibility the property getters still work; they delegate to the ModelMetadata property to retrieve the value. Changes in ASP.NET MVC 2 Preview 1 Changes to the DefaultControllerFactory class break custom controller factories that derive from it The DefaultControllerFactory class was fixed by removing the RequestContext property. In place of this property, the request context instance is passed to the protected virtual GetControllerInstance and GetControllerType methods. This change affects custom controller factories that derive from DefaultControllerFactory. Custom controller factories are often used to provide dependency injection for ASP.NET MVC applications. To update the custom controller factories to support ASP.NET MVC 2, change the method signature or signatures to match the new signatures, and use the request context parameter instead of the property. “Area” is a now a reserved route-value key The string “area” in Route values now has special meaning in ASP.NET MVC, in the same way that “controller” and “action” do. One implication is that if HTML helpers are supplied with a route-value dictionary containing “area”, the helpers will no longer append “area” in the query string. If you are using the Areas feature, make sure to not use {area} as part of your route URL. Known Issues Adding a debugger watch that shows a value from TempData will mark it for deletion. The side effect was introduced as part of the changes to TempDataDictionary. Disclaimer This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication. This White Paper is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred. © 2009 Microsoft Corporation. All rights reserved. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Claude Code VS Code扩展：多文件协同编程的智能协作者

AI编程助手正从代码补全迈向智能协作者阶段，其核心在于理解项目语义、执行真实IDE操作并深度集成开发工作流。Claude Code作为Anthropic官方VS Code扩展，依托MCP协议与本地代理架构，在保障数据不出本地的前提下，实现跨文件分析、结构化上下文注入与可审查的多步编辑。它不替代开发者决策，而是通过图形化意图翻译、计划模式（Plan Mode）和CLAUDE.md项目宪法机制，将重构、调试、测试等高心智负荷任务转化为可追溯、可回滚的原子操作。适用于中大型工程的全链路协同开发场景。

DP83848CVV.pdf

National_Semiconductor的一款网络芯片的技术手册。1.0 Pin Descriptions m 9 1.1 Serial Management Interface 9 1.2 MAC Data Interface .9 1.3 Clock Interface 11 1. 4 LED Interface 1.5 Reset and Power down 12 1.6 Strap Options 12 1.7 10 Mb/s and 100 Mb/s PMD Interface 14 1.8 Special Connections 14 1. 9 Power Supply Pi 14 1. 10 Package Pin AsSi 15 2.0 Configuration 16 2. 1 Auto-Negotiation g 16 2.1.1 Auto-Negotiation Pin Control 16 2.1.2 Auto-Negotiation Register Control 16 2.1.3 Auto-Negotiation Parallel Detection 2. 1. 4 Auto-Negotiation Restart 2.1.5 Enabling Auto-Negotiation via Software 17 2.1.6 Auto-Negotiation Complete Time 17 2.2 Auto-MDIX 2. 3 PHY Address 18 2.3.1 Mll Isolate mode 2.4 LED Interface 19 2.4.1LED 19 2.4.2 LED Direct Control 2.5 Half Duplex VS Full Duplex 20 2.6 Internal Loopback 20 2.7 BIST 20 3.0 Functional Description .I.I... 21 3.1 Mll Interface 3.1.1 Nibble-wide mll data Interface 21 3.1.2 Collision detect 3.1.3 Carrier Sense 21 3.2 Reduced mll Interface 3.3 10 Mb Serial Network Interface(SNI) .22 3. 4 802.3u Mll Serial Management Interface 3.4.1 Serial Management Register Access 3.4.2 Serial Management Access protocol 22 3.4.3 Serial Management Preamble Suppression 4.0 Architecture 24 4.1100BASE-TX TRANSMITTER .24 4.1. 1 Code-group Encoding and Injection 26 4.1.2 Scrambler 26 4.1 3 Nrz to nrzi Encoder 26 4.1. 4 Binary to MLT-3 Convertor 26 4.2100 BASE-T×RECEⅣVER 26 4.2.1 Analog Front Et 26 4.2.2 Digital Signal Processor 26 4.2.2.1 Digital Adaptive Equalization and gain Control 28 4.2.2.2 Base Line Wander Compensation 4.2.3 Signal detect 4.2.4 MLT-3 to nrzi Decoder 4,25 nrz to nrz 4.2.6 Serial to parallel 4.2.7 Descrambler 4.2.8 Code-group Alignment 4.29 4B/5B Decoder 4.2. 10 100BASE-TX Link Integrity Monitor ..30 42. 11 Bad ssD Detection .30 www.national.com Oo寸∞∞∞ 4.3 10BASE-T TRANSCEIVER MODULE 30 4.3.1 Operational Modes 30 4.3.2 Smart squelch 31 4.3.3 Collision Detection and sQE 4.3.4 Carrier Sense 31 4.3.5 Normal Link Pulse detection/Generation 4.3.6 Jabber function …32 4.3. 7 Automatic Link Polarity detection and correction .....32 4.3.8 Transmit and Receive Filtering ...32 4.3.9 Transmitter 4.3.10 Receiver 5.0 Design Guidelines 33 5. 1 TPI Network circuit ....33 5.2 ESD Protection 34 5.3 Clock In(X1) Requirements 34 5. 4 Power feedback circu 35 5.5 Power Down/Interrupt 35 5.5.1 Power down control mode ....35 5.5.2 Interrupt Mechanisms 5.6 Energy Detect Mode 36 6.0 Reset Operation..∴.∴∴∴.37 6.1 Hardware reset 6.2 Software reset 7.0 Register Block ,,,,,,,,,38 7. 1 Register definition 7.1.1 Basic Mode Control Register(BMCR) 7.1.2 Basic Mode Status Register(BMSR) 44 7.1.3 PHY Identifier Register #1 (PHYIDR1) 45 7.1. 4 PHY Identifier Register #2(PHYIDR2 ..45 7.1.5 Auto-Negotiation Advertisement Register(ANAR) .......45 7.1.6 Auto-Negotiation Link Partner Ability Register(ANLPAR) (BASE Page) 7.1.7 Auto-Negotiation Link Partner Ability Register(ANLPAR)(Next Page) 7.1.8 Auto-Negotiate Expansion Register (ANER) 7.1.9 Auto-Negotiation Next Page Transmit Register(ANNPTR) 7.2 EXtended Registers 50 7.2.1 PHY Status Register(PHYSTS 7.2.2 Mll Interrupt Control Register(MICR 52 7.2.3 MIl Interrupt Status and Misc. Control Register(MISR) 7.2.4 False Carrier Sense Counter Register(FCSCR) 7.2.5 Receiver Error Counter Register(RECR 7.2.6 100 Mb/s PCS Configuration and Status Register(PCSR) 55 7.2.7 RMII and Bypass Register(RBR) 7. 2. 8 LED Direct Control Register(LEDCR 7. 2. 9 PHY Control Register(PHYCR) .....57 7.2.10 10Base-T Status/Control Register(1OBTSCR) 58 7. 2.11 CD Test and BIST Extensions Register(CDCTRL1) 60 7. 2. 12 Energy Detect Control (EDCR) 6 8.0 Electrical Specifications 62 8.1 DC Specs 62 8.2 AC Specs .,,,,.,64 8.2.1 Power Up Timing 64 8.2.2 Reset Timing 8.2.3 Mll Serial Management Timing 8.2.4 100 Mb/s MIl Transmit Timing 8.2.5 100 Mb/s Mll Receive Timing ............67 8.2.6 100BASE-TX Transmit Packet Latency Timing 67 8.2.7 100BASE-TX Transmit Packet Deassertion Timing 8.2.8 100BASE-TX Transmit Timing(tr/F&amp; Jitter) 8.2.9 100BASE-TX Receive Packet Latency Timing 70 8.2.10 100BASE-TX Receive Packet Deassertion Timing 70 www.national.com 8.2.11 10 Mb/s Mll Transmit Timing 71 8.2.12 10 Mb/s Mll Receive Timing 8.2.13 10 Mb/s serial Mode Transmit Timing 8.2.14 10 Mb/s serial Mode Receive timing 8.2.15 10BASE-T Transmit Timing (Start of Packet 73 8.2. 16 10BASE-T Transmit Timing(End of Packet 73 8. 2. 17 10BASE-T Receive Timing(Start of Packet) 8.2.18 10BASE-T Receive Timing(End of Packet 74 8.2.19 10 Mb/s heartbeat Timing 75 8.2.20 10 Mb/s Jabber Timing 8222 Auto-Negotiation Fast Link Pulse(FLP) Timing…、∴ 8.2.21 10BASE-T Normal Link Pulse Timing .....,,,,76 8.2.23 100BASE-TX Signal Detect Timing 8.2.24 100 Mb/s Internal loopback timing 8.2.25 10 Mb/s Internal Loopback Timing .78 8. 2.26 RMII Transmit Timing .79 8.2.27 RMII Receive Timing 82.28 Isolation Timing 81 8.2.29 25 MHz OUT Timing 81 8.2.30 100 Mb/s X1 to TX CLK Timing 82 9.0 Physical Dimensions∴∴ ■■■ 84 ww.national. com Oo寸∞∞∞ List of Figures Figure 1. DP83848C Functional Block Diagram..... Figure 2. PHYAD Strapping Example 18 Figure 3. AN Strapping and LED Loading Example 19 Figure 4. Typical MDC/MDIO Read Operation ......23 Figure 5. Typical MDC/MDIO Write Operation 23 Figure 6. 100BASE-TX Transmit Block Diagram ,,,,,,.,,.24 Figure 7. 100BASE-TX Receive Block Diagram 27 Figure 8. EIA/TIA Attenuation Vs Frequency for 0, 50, 100, 130&amp;150 meters of CAt 5 cable...... 28 Figure 9. 100BASE-TX BLW Event ........ Figure 10. 10BASE-T Twisted Pair Smart Squelch Operation 31 Figure 11 10/100 Mb/s Twisted Pair Interface...,.......... 33 Figure 12. Crystal Oscillator Circuit 34 Figure 13. Power Feeback Connection 35 www.national.com List of tables Table 1. Auto-Negotiation Modes .16 Table 2. PHY Address Mapping Table 3. lEd Mode select 19 Table 4. Supported packet sizes at +/-50ppm +/-100ppm for each clock Table 5. Typical MDIO Frame Format Table 5. 4B5B Code-Group Encoding/Decoding Table 6. 25 .,34 Table7.25 MHz Oscillator Specification∴.∴.∴ ,,,,,,,,,,34 Table 8. 50 MHz Oscillator Specification ,,35 Table 9. 25 MHz Crystal Specification Table 10 Register Map...................... 38 Table 11. Register Table ..∴......39 Table 12. Basic Mode Control Register (BMCR), address 0X00 Table 13. Basic Mode Status Register(BMSR), address 0x01 Tabe14. PHY ldentifier Register#1( PHYIDR1), address0x02.∴………………………4 Table 15 PHY Identifier Register #2 (PHYIDR2), address 0x03 45 Table 16. Negotiation Advertisement Register(ANAR), address 0x04 45 Table 17. Auto-Negotiation Link Partner Ability Register(ANLPAR)(BASE Page), address 0x05.... 46 Table 18 Auto-Negotiation Link Partner Ability Register(ANLPAR)(Next Page), address 0x05..... 48 Table 19. Auto-Negotiate Expansion Register(ANER), address 0X06 Table 20 Auto-Negotiation Next Page Transmit Register(ANNPTR), address 0x07 .∴.∴......,49 Table 21. PHY Status Register(PHYSTS), address 0x10 Table 22 Mll Interrupt Control Register(MICR), address 0x11 n..52 Table 23. MIl Interrupt Status and Misc. Control Register(MISR), address 0x12 .....∴.53 Table 24. False Carrier Sense Counter Register(FCSCR), address 0x14 54 Table 25 Receiver Error Counter Register(RECR), address 0x15 54 Table 26. 100 Mb/s PCS Configuration and Status Register(PCSR), address 0x16 Table 27. RMI and Bypass Register(RBR), addresses 0x17...................56 Table 28 LED Direct Control Register (LEDCR), address 0X18 量重面 重重m 56 Table 29 PHY Control Register(PHYCR), address Ox19 57 Table 30 10Base-T Status/Control Register(10BTSCR), address OX1A Table 31. CD Test and BIST Extensions Register(CDCTRL1), address 0x1B ..60 Table 32. Energy Detect Control (EDCR), address 0x1D ,,61 www.national.com Oo寸∞∞∞ In Layou 乙uzoOHOau PFBIN2 24 RBIAS 23上 PFBOU RX DV/MIL MODE AVDD33 CRS/CRS DV/LED CFG RESERVED RX ER/MDIX EN 41 RESERVED 42 RXD O/PHYAD1 DP838480 PFBIN1 RXD 1/PHYAD2 Td RXD 2/PHYAD3 TD RXD 3/PHYAD4 AGND OGND JOVDD33 Hz=z3oa au&gt;u c u&gt;uOu p vie NS Package Number Vbh48A www.national.com 1.0 Pin Descriptions The DP83848C pins are classified into the following inter- All DP83848C signal pins are i/o cells regardless of the face categories(each interface is described in the sections particular use. The definitions below define the functionality that follow of the l/O cells for each pin Serial Management Interface Input MAC Data Interface Output Clock Interface Type: I/o Input/Output LED Interface Type OD Open Drain Reset and power down Type: PD, PU Internal Pulldown/Pullup Strap Options Strapping Pin(All strap pins have weak in- --10/100 Mb/s Pmd Interface ternal pull-ups or pull-downs. If the default Special Connect Pins strap value is needed to be changed then an external 2.2 k resistor should be used Power and ground pins Please see Section 1.6 for details.) Note: Strapping pin option. Please see Section 1.6 for strap definitions 1.1 Serial Management Interface Signal Name Tvpe Pin t Description MDC 31 MANAGEMENT DATA CLOCK: Synchronous clock to the MDIo management data input/output serial interface which may be asynchronous to transmit and receive clocks. The maximum clock rate is 25 Mhz with no minimum clock rate MDIO 30 MANAGEMENT DATA l/O: Bi-directional management instruc tion/data signal that may be sourced by the station management entity or the PhY. This pin requires a 1.5k pullup resistor 1.2 MAC Data Interface Signal name Type Pin t Description TX CLK MII TRANSMIT CLOCK: 25 MHz Transmit clock output in 100 Mb/s mode or 2.5 MHz in 10 mb/s mode derived from the 25 mHz reference clock Unused in emil mode the device uses the x1 reference clock in put as the 50 MHz reference for both transmit and receive SNI TRANSMIT CLOCK: 10 MHZ Transmit clock output in 10 Mb SNI mode. The MAc should source TX EN and TXdO using this clock TX EN L PD Mll TRANSMIT ENABLE: Active high input indicates the pres ence of valid data inputs on TXD3: 0 RMII TRANSMIT ENABLE: Active high input indicates the pres- ence of valid data on TXD[1: 0 SNI TRANSMIT ENABLE: Active high input indicates the pres- ence of valid data on TXD 0 TXD 0 MII TRANSMIT DATA: Transmit data Mll input pins, TXD3: 0 TXD 1 3456 that accept data synchronous to the TX ClK (2.5 MHz in 10 Mb/s mode or 25 MHz in 100 Mb/s mode) TXD 2 RMII TRANSMIT DATA: Transmit data RMII input pins, TXD[1 TXD 3 S.L. PD that accept data synchronous to the 50 MHz reference clock SNI TRANSMIT DATA: Transmit data sNi input pin TXd 0, that accept data synchronous to the TX CLK (10 MHz in 10 Mb/s sni mode) www.national.com Oo寸∞∞∞ Signal name Type Pin #i Description RX CLK 38 MI RECEE CLOCK: Provides the 25 mhz recovered receive clocks for 100 Mb/s mode and 2.5 MHz for 10 Mb/s mode Unused in rmll mode the device uses the xl reference clock in put as the 50 MHz reference for both transmit and receive SNI RECEIVE CLOCK: Provides the 10 MHz recovered receive clocks for 10 Mb/s sni mode RXD∨ S.O. PD MII RECEIVE DATA VALID: Asserted high to indicate that valid data is present on the corresponding RXD[3: 0]. MIl mode by de fault with internal pulldown RMII Synchronous Receive Data Valid: This signal provides the RMII Receive Data valid indication independent of carrier sense This pin is not used in SNI mode RX ER S.O. PU MIl RECEIVE ERROR: Asserted high synchronously to RX CLK to indicate that an invalid symbol has been detected within a re ceived packet in 100 Mb/s mode RMII RECEIVE ERROR: Assert high synchronously to X1 when- ever it detects a media error and rxdv is asserted in 100 mb/s This pin is not required to be used by a mac, in either mil or rmll mode, since the Phy is required to corrupt data on a receive error This pin is not used in SNI mode RXD O S.O. PD MII RECEIVE DATA: Nibble wide receive data signals driven syn RXd 1 chronously to the rx clk, 25 Mhz for 100 Mb/s mode 2.5 MHZ for 10 Mb/s mode ) RXD[3 0] signals contain valid data when RXD 2 45 RX DV is asserted RXD 3 46 RMII RECEIVE DATA: 2-bits receive data signals, RXD[1: 0], driv en synchronously to the X1 clock, 50 MHZ SNI RECEIVE DATA: Receive data signal, RXD 0, driven syn chronously to the RX ClK RXd0 contains valid data when CRs is asserted. RXD[3: 1] are not used in this mode CRS/CRS DV S.O. PU MII CARRIER SENSE: Asserted high to indicate the receive me dium is non idle RMII CARRIER SENSE/RECEIVE DATA VALID: This signal combines the rmll carrier and receive data valid indications For a detailed description of this signal, see the RMII Specifica- SNI CARRIER SENSE: Asserted high to indicate the receive me dium is non -idle. It is used to frame valid receive data on the RXD 0 signal COL S.O. PU MI COLLISION DETECT: Asserted high to indicate detection of a collision condition(simultaneous transmit and receive activity) in 10 Mb/s and 100 Mb/s Half Duplex Modes While in 10BASE-T Half Duplex mode with heartbeat enabled this pin is also asserted for a duration of approximately 1 s at the end of transmission to indicate heartbeat (SQE test In Full duplex Mode, for 10 Mb/s or 100 Mb/s operation, this sig nal is always logic 0. There is no heartbeat function during 10 Mb/s full duplex operation RMII COLLISION DETECT: Per the RMll Specification, no COL signal is required. The MAc will recover CRS from the CRS DV signal and use that along with its tX en signal to determine col- SNI COLLISION DETECT: Asserted high to indicate detection of a collision condition(simultaneous transmit and receive activity) in 10 Mb/s sni mode www.national.com 10

新手AI入门工具选择指南：从Colab到VS Code的渐进路径

AI开发工具并非指底层框架，而是帮助初学者建立‘输入→处理→输出’确定性闭环的认知脚手架。理解这一本质，是区分玩具实验与工程实践的关键起点。Google Colab以零配置环境降低入门门槛，Hugging Face Spaces将模型能力封装为可交互Web界面，Kaggle Notebooks提供真实脏数据训练场，Streamlit用Python语法实现前端逻辑，而VS Code则推动开发者跨越到软件工程规范。这些工具共同构成一条‘认知负荷递增’的学习链，覆盖从快速验证、作品集构建到生产部署的全周期需求。本

VS2026中文乱码问题解决方案与编码设置指南

字符编码是软件开发中的基础概念，从ASCII到Unicode的演进解决了多语言支持问题。UTF-8作为通用编码方案，通过变长字节表示字符，既兼容ASCII又支持全球语言。在VS2026开发环境中，编码设置涉及文件存储、编辑器显示、控制台输出等多个环节，不当配置会导致中文乱码问题。通过系统区域设置调整、字体配置检查和项目级编码统一，可以有效解决源代码乱码、输出异常等典型问题。特别是在团队协作开发场景中，统一的.editorconfig配置和Git编码设置能确保跨环境一致性。掌握这些编码处理技巧，对提升C++、